Method and system for managing parking by dual location verification

ABSTRACT

A computerized system for managing a parking lot includes: a beacon in one-way, or location sensor in two-way, communication with a smart device for locating the smart device without it having to determine its own location, a vehicle sensor for sensing the presence of a vehicle, and a computer-implemented server operable to determine from the beacon&#39;s identification or receive from the location sensor the location of the smart device. The server authorizes entry or exit of the vehicle when a smart device status indicates acceptance, and the smart device and the vehicle are both at a same appropriate location. The server updates the smart device status after a payment transaction. Entry or exit may be authorized by opening a barrier, displaying an authorization message, communicating a message to the smart device, and/or not issuing a non-authorization alert. The server may receive reservations, and may communicate lot occupancy to third-party systems.

BACKGROUND OF THE INVENTION

1. Field of Invention

This invention relates to the management of vehicle parking sessionsand, in particular, to a method and system for managing parking by duallocation verification.

2. Description of Related Art

Managing the parking of vehicles involves granting to selected vehiclesaccess to parking stalls and receiving payment for parking from thevehicle operators.

In conventional parking management systems, human intervention isinvolved in many aspects of vehicle parking management.

Some automated parking systems reduce the amount of human interventionrequired, but do not eliminate the need for human intervention. Forexample, in controlled parking lots human intervention is often neededto operate an access gate to ensure payment is received for parking. Inuncontrolled parking lots without a human-operated gate, humanintervention is often needed to patrol the parking lot to locateinstances of unpaid parking.

U.S. Pat. No. 8,131,596 to McQuilken discloses a method and system ofpayment for parking using a smart device and an in-vehicle displaydevice for indicating parking payment status in a manner that is visibleor can be scanned or sensed by parking enforcement personnel. The smartdevice is in wireless communication with the in-vehicle display devicepositioned for viewing or scanning by meter enforcement personnel.However, the in-vehicle display device must be obtained in advance bythe vehicle owner and, once obtained, it is vulnerable to tampering,other damage, and theft.

United States patent application publication No. 2012/0130775 to Bogaardet al. discloses a method for processing a transaction for a parkingsession wherein the user facilitates the transaction through a mobilecomputing device of the user. However, the method of Bogaard et al.requires that the mobile computing device receive a parking identifier,such as by the user typing the parking identifier into the mobilecomputing device or otherwise in response to a user input action.

International publication No. WO2004/070674 to Kim discloses a parkingcontrol system using a mobile phone. However, the system of Kim requiresthat the parking person telephone a parking control server and input aparking position serial number indicative of a parking section positionwhere his or her vehicle parks.

U.S. Pat. No. 7,319,974 to Brusseaux discloses a vehicle parkingmanagement method involving short-distance communication, such as byBluetooth™ communication, between a mobile telephone of the user and aparking ticket machine. However, the method of Brusseaux requires thatthe user enter on his or her telephone a message including informationabout the user's identity and information concerning the parking time,and possibly information concerning the vehicle parking location andpossibly information identifying the parked vehicle. When the userdecides to vacate the parking space, the user must send a secondtelephone message to the ticket machine that includes informationconcerning the identification of the parked vehicle and the parking endtime.

U.S. Pat. No. 7,114,651 to Hjelmvik discloses a method for control ofparked vehicles in which a vehicle-specific code is tied to auser-specific code in a parking system computer. However, the method ofHjelmvik requires a parking attendant send a voice message to atelephone coupled to the parking system computer indicating a vehicleregistration number.

U.S. Pat. No. 6,889,899 to Silberberg discloses a vehicle parkingsystem. However, the system of Silberberg requires that the user dial atelephone number of a central control station computer and also inputthe user's account number and a number identifying a parking meter orother parking pay number.

An object of the invention is to address the above shortcomings.

SUMMARY

The above shortcomings may be addressed by providing, in accordance withone aspect of the invention, a computer-implemented method of managing aparking lot. The method involves: (a) authorizing an entry of a firstvehicle by a computerized parking controller in response to a statusindicating no entry rejection of a smart device, a first locationindicating that the smart device is located at an entry location of theparking lot, and a first presence indicating that the first vehicle ispresent at the entry location, the first location being determined bythe parking controller in response to an entry-beacon identification ofan entry beacon of the parking lot, the entry-beacon identificationbeing communicated to the parking controller by the smart device in afirst communication; (b) determining by the parking controller anupdated value of the status in response to a payment transactionassociated with the smart device; and (c) authorizing an exit of asecond vehicle by the parking controller in response to the statusindicating no exit rejection of the smart device, a second locationindicating that the smart device is located at an exit location of theparking lot, and a second presence indicating that the second vehicle ispresent at the exit location, the second location being determined bythe parking controller in response to an exit-beacon identification ofan exit beacon of the parking lot, the exit beacon being selected fromthe group consisting of the entry beacon and another beacon separatefrom the entry beacon, the exit-beacon identification being communicatedto the parking controller by the smart device in a second communication,the exit location being selected from the group consisting of the entrylocation and another location separate from the entry location, thesecond vehicle being the first vehicle or another vehicle separate fromthe first vehicle.

Step (c) may involve determining by the parking controller whether thesecond vehicle is identified as the first vehicle. The parking lot mayhave an entry barrier for regulating entries at the entry location. Step(a) may involve opening the entry barrier by the parking controller soas to authorize the entry of the first vehicle. The parking lot may havean exit barrier for regulating exits at the exit location. Step (c) mayinvolve opening the exit barrier by the parking controller so as toauthorize the exit of the second vehicle. The exit barrier may beselected from the group consisting of the entry barrier and anotherbarrier separate from the entry barrier. Step (a) may involve receivingby the parking controller the first communication generated by the smartdevice in response to the smart device receiving no more than a singleuser command entered into the smart device. Step (c) may involvereceiving by the parking controller the second communication generatedby the smart device in response to the smart device receiving no morethan a single user command entered into the smart device. Step (a) mayinvolve authorizing the entry of the first vehicle in response to anidentification of the smart device selected from the group consisting ofa telephone number, device identification code, licence plate number, animage of a licence plate, driver's licence number, an image of adriver's licence, officially-issued identification number, an image ofan officially-issued identification certificate, a vehicleidentification code, and a financial card number. Step (c) may involveauthorizing the exit of the second vehicle in response to the statusindicating that the smart device is registered with the parkingcontroller and is in compliance with payment requirements of the parkingcontroller. Step (a) may involve authorizing the entry of the firstvehicle in response to the status indicating that the smart device isregistered with the parking controller and is in compliance with paymentrequirements of the parking controller. The method may further involvesdetermining by the parking controller a parking fee in response to aparking rate associated with the smart device. Determining by theparking controller a parking fee in response to a parking rateassociated with the smart device may involve determining the parking feein response to a duration of time spent parking. Determining the parkingfee in response to a duration of time spent parking may involvedetermining the parking fee in response to the duration of time elapsedbetween when the parking controller authorizes the entry of the firstvehicle and when the parking controller determines the second location.Step (a) may involve opening a stall barrier by the parking controllerso as to authorize the entry of the first vehicle. The method mayfurther involve opening a second entry barrier by the parking controllerin response to the status indicating no second-entry rejection and to athird location determined by the parking controller, the third locationindicating that the smart device is located in proximity to an entranceside of the second entry barrier. Opening a second entry barrier by theparking controller in response to the status indicating no second-entryrejection and to a third location determined by the parking controller,the third location indicating that the smart device is located inproximity to an entrance side of the second entry barrier, comprisesopening a stall barrier. The method may further involve determining bythe parking controller a parking fee in response to a parking rateassociated with the smart device and a duration of time spent parking.Determining by the parking controller a parking fee in response to aparking rate associated with the smart device and a duration of timespent parking may involve determining the parking fee in response to theduration of time elapsed between when the parking controller determinesan entry associated with the stall barrier and when the parkingcontroller determines an exit associated with the stall barrier. Themethod may further involve communicating by the parking controller to atleast one of the smart device and a computerized third-party system anotification generated by the parking controller in response to theparking controller authorizing the entry of the first vehicle, thenotification indicating the entry of the first vehicle in associationwith the smart device. The method may further involve communicating bythe parking controller to at least one of the smart device and acomputerized third-party system a notification generated by the parkingcontroller in response to the parking controller authorizing the exit ofthe second vehicle, the notification indicating the exit of the secondvehicle in association with the smart device. The method may furtherinvolve communicating by the parking controller to at least one of thesmart device and a computerized third-party system a notificationgenerated by the parking controller in response to the second entrybarrier being opened, the notification indicating the entry of the firstvehicle in association with the smart device. The method may involvereceiving by the parking controller a parking reservation requestassociated with the smart device and the parking lot. Receiving by theparking controller a parking reservation request associated with thesmart device and the parking lot may involve receiving the parkingreservation request from a computerized parking reservation system. Themethod may further involve determining by the parking controller a lotoccupancy for the parking lot by maintaining a count of the differencebetween the number of authorized entries and authorized exits. Themethod may further involve communicating by the parking controller thelot occupancy to a third-party computerized system. Communicating by theparking controller the lot occupancy to a third-party computerizedsystem may involve communicating to a computerized parking reservationsystem. The method may involve receiving by the parking controller fromthe computerized parking reservation system a parking reservationrequest associated with the smart device and the parking lot. The methodmay further involve closing the entry barrier by the parking controllerin response to a third presence determined by the parking controller,the third presence indicating that the first vehicle is present at aninterior side of the entry barrier. The method may further involveclosing the exit barrier by the parking controller in response to athird presence determined by the parking controller, the third presenceindicating that the second vehicle is present at an exterior side of theexit barrier. The method may further involve communicating by the serverto the smart device parking lot information associated with the parkinglot, the parking lot information including the location of the parkinglot. The method may further involve communicating by the server to thesmart device a notification of expiry of at least one of a parkingsession and a parking reservation. The method may further involvecommunicating by the server to a third-party computerized system anotification of expiry of at least one of a parking session and aparking reservation.

In accordance with another aspect of the invention, there is provided acomputerized system for managing a parking lot. The system includes: (a)an entry beacon operable to transmit an entry-beacon identification ofthe entry beacon; (b) an exit beacon operable to transmit an exit-beaconidentification of the exit beacon, the exit beacon being selected fromthe group consisting of the entry beacon and another beacon separatefrom the entry beacon; (c) a first vehicle sensor operable to sense thepresence of a first vehicle at a vehicle entry location of the parkinglot; (d) a second vehicle sensor operable to sense the presence of asecond vehicle at a vehicle exit location of the parking lot, the secondvehicle sensor being selected from the group consisting of the firstvehicle sensor and another vehicle sensor separate from the firstvehicle sensor, the exit location being selected from the groupconsisting of the entry location and another location separate from theentry location, the second vehicle being the first vehicle or anothervehicle separate from the first vehicle; and (e) a computer-implementedserver operable to receive from a smart device each of the entry-beaconidentification and the exit-beacon identification, operable to determinethe location of the smart device in response to said each of theentry-beacon identification and the exit-beacon identification, operableto determine a status associated with the smart device, operable toauthorize an entry of the first vehicle when the status indicates noentry rejection of the smart device, the determined location of thesmart device is at the entry location, and the first vehicle sensorsenses the presence of the first vehicle at the entry location, operableto determine an updated value of the status in response to a paymenttransaction associated with the smart device, and operable to authorizean exit of a second vehicle when the status indicates no exit rejectionof the smart device, the determined location of the smart device is atthe exit location, and the second vehicle sensor senses that the secondvehicle is at the exit location.

The parking lot may have an entry barrier for regulating entries at theentry location. The system may include an entry controller operable toopen and close the entry barrier. The server may be operable to causethe entry controller to open the entry barrier when the serverauthorizes the entry of the first vehicle. The parking lot may have anexit barrier for regulating exits at the exit location. The system mayinclude an exit controller operable to open and close the exit barrier.The server may be operable to cause the exit controller to open the exitbarrier when the server authorizes the exit of the second vehicle. Theexit barrier may be selected from the group consisting of the entrybarrier and another barrier separate from the entry barrier. The exitcontroller may be selected from the group consisting of the entrycontroller and another controller separate from the entry controller.The server may be operable to determine a parking fee associated withthe smart device in response to a duration of time spent parking.

In accordance with another aspect of the invention, there is provided acomputerized system for managing a parking lot. The system includes: (a)means for authorizing an entry of a first vehicle in response to astatus indicating no entry rejection of a smart device, a first locationindicating the smart device is located at an entry location of theparking lot, and a first presence indicating that the first vehicle ispresent at the entry location; (b) means for determining an updatedvalue of the status in response to a payment transaction associated withthe smart device; and (c) means for authorizing an exit of a secondvehicle in response to the status indicating no exit rejection of thesmart device, a second location indicating that the smart device islocated at an exit location of the parking lot, and a second presenceindicating that the second vehicle is present at the exit location, theexit location being selected from the group consisting of the entrylocation and another location separate from the entry location, thesecond vehicle being the first vehicle or another vehicle separate fromthe first vehicle.

The system may include means for determining whether the second vehicleis the first vehicle.

In accordance with another aspect of the invention, there is provided acomputer-implemented method of managing a parking lot. The methodinvolves: (a) authorizing an entry of a first vehicle by a computerizedparking controller in response to a status indicating no entry rejectionof a smart device, a first location indicating that the smart device islocated at an entry location of the parking lot, and a first presenceindicating that the first vehicle is present at the entry location, thefirst location being determined by a location sensor of the parkingcontroller, the location sensor being operable to determine the locationof the smart device when the smart device is within a near-field rangeof the location sensor, the location sensor communicating the firstlocation to a server of the parking controller; (b) determining by theparking controller an updated value of the status in response to apayment transaction associated with the smart device; and (c)authorizing an exit of a second vehicle by the parking controller inresponse to the status indicating no exit rejection of the smart device,a second location indicating that the smart device is located at an exitlocation of the parking lot, and a second presence indicating that thesecond vehicle is present at the exit location, the second locationbeing determined by the location sensor, the location sensorcommunicating the second location to the server, the exit location beingselected from the group consisting of the entry location and anotherlocation separate from the entry location, the second vehicle being thefirst vehicle or another vehicle separate from the first vehicle.

Step (a) may involve determining by the location sensor the firstlocation by trilateration of at least one first communication betweenthe smart device and a plurality of wireless communication devices ofthe location sensor disposed at the parking lot. Step (c) may involvedetermining by the location sensor the second location by trilaterationof at least one second communication between the smart device and theplurality of wireless communication devices. Step (a) may involveeffecting the at least one first communication by near-field wirelesscommunications. Step (c) may involve effecting the at least one secondcommunication by near-field wireless communications. Step (a) mayinvolve determining by the location sensor the first location byproximity sensing the smart device by a first proximity sensor of thelocation sensor disposed at the parking lot. Step (c) may involvedetermining by the location sensor the second location by proximitysensing the smart device by a second proximity sensor of the locationsensor disposed at the parking lot. The second proximity sensor may beselected from the group consisting of the first proximity sensor andanother proximity sensor separate from the first proximity sensor. Step(a) may involve determining by the location sensor the first location byestablishing near-field communication between the smart device and afirst NFC device of the location sensor disposed at the parking lot.Step (c) may involve determining by the location sensor the secondlocation by establishing near-field communication between the smartdevice and a second NFC device of the location sensor disposed at theparking lot. The second NFC device may be selected from the groupconsisting of the first NFC device and another NFC device separate fromthe first NFC device.

Other aspects and features of the present invention will become apparentto those of ordinary skill in the art upon review of the followingdescription of embodiments of the invention in conjunction with theaccompanying figures and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In drawings which illustrate by way of example only embodiments of theinvention:

FIG. 1 is a block diagram of a computerized system for managing aparking lot according to a first embodiment of the invention;

FIG. 2 is a signal timeline chart for the system shown in FIG. 1,showing the communication of messages between system componentsincluding an entry controller;

FIG. 3 is a signal timeline chart for the system shown in FIG. 1,showing the communication of messages between system componentsincluding an exit controller;

FIG. 4 is a first portion of a flow diagram of a computer-implementedmethod of managing a parking lot according to the first embodiment ofthe invention, showing method steps associated with an entry request;

FIG. 5 is a second portion of the flow diagram shown in FIG. 4, showingmethod steps associated with an exit request; and

FIG. 6 is a flow diagram of an exemplary method for performing steps ofcollecting a parking fee in accordance with the second portion shown inFIG. 5, showing initiation of a payment transaction.

DETAILED DESCRIPTION

A computerized system for managing a parking lot includes: (a) means forauthorizing an entry of a first vehicle in response to a statusindicating no entry rejection of a smart device, a first locationindicating the smart device is located at an entry location of theparking lot, and a first presence indicating that the first vehicle ispresent at the entry location; (b) means for determining an updatedvalue of the status in response to a payment transaction associated withthe smart device; and (c) means for authorizing an exit of a secondvehicle in response to the status indicating no exit rejection of thesmart device, a second location indicating that the smart device islocated at an exit location of the parking lot, and a second presenceindicating that the second vehicle is present at the exit location, theexit location being selected from the group consisting of the entrylocation and another location separate from the entry location, thesecond vehicle being the first vehicle or another vehicle separate fromthe first vehicle. The system may include means for determining whetherthe second vehicle is the first vehicle.

Referring to FIG. 1, the system according to a first embodiment of theinvention is shown generally bounded within a dotted-line rectangle at10.

The system 10 is operable to manage a parking lot (not shown) typically,but not necessarily, having an entry barrier such as an entrance gate(not shown) and an exit barrier such as an exit gate (not shown), and assuch the system 10 may be referred to as a computerized parkingcontroller. The entrance gate or other entry barrier, if present,defines an entry lane (not shown) leading up to the entrance gate. Theportion of the entry lane that is on the exterior side of the entrancegate may be part of the parking lot, a public alley or other roadway, aprivate driveway, a similar access lane, or any combination thereof, forexample. Typically, at least one entrance gate is located along theouter perimeter of the parking lot such that the portion of the entrylane that is on the interior side of the entrance gate is inside theparking lot. The entry lane on the interior side of the entrance gateordinarily proceeds from the entrance gate to provide access to anynumber of parking stalls (not shown) of the parking lot. The parkingstalls may be marked (e.g. by painted lines, such as on asphalt orconcrete, signposts, signs, etc.) or may be unmarked (e.g. in the caseof a gravel or grass parking lot), for example.

Similarly, the exit gate or other exit barrier, if present, defines anexit lane (not shown) leading up to the exit gate. The portion of theexit lane that is on the interior side of the exit gate forms part ofthe parking lot between the parking stalls and the exit gate. Typically,at least one exit gate is located along the outer perimeter of theparking lot, such that the portion of the gated exit lane that is on theexterior side of the exit gate is outside of the parking lot. The gatedexit lane on the exterior side of the exit gate ordinarily proceeds fromthe exit gate away from the parking lot and connects to public roadwaysor the like.

Typically, the entrance and exit gates are adjacent to each other suchthat the entry lane and the exit lane on both the interior and exteriorsides of their respectively associated gates are adjacent to each otherand not overlapping with each other. However, in some embodiments theexit and entrance gates are adjacent, non-overlapping portions of asingle, larger gate (e.g. a roll gate spanning the entry and exitlanes). In such embodiments, the entrance gate and the exit gate openand close simultaneously. For example, the entrance and exit gates maybe integrally connected to each other to form the single gate.

In some embodiments, the entry and exit lanes coincide with each otherto form a single entry-and-exit lane. In such embodiments, the entrancegate and the exit gate are typically integrally connected to each otherto form a single gate, which would ordinarily span the singleentry-and-exit lane.

In general, any suitable barrier or barriers for regulating entries intoand exits from the parking lot may be employed. A barrier may beimplemented by any suitable type of gate such as a rotating gate,horizontally sliding gate, roll gate, etc.; any suitable type ofblockade such as spikes, posts, beams, etc.; any suitable type ofspanning catenary such as a chain, wire, cable, rope, ribbon, etc.; andany suitable type of indicator such as a red/green light, audiblecommand, text and/or graphic display, etc.; any suitable messagecommunicated to a vehicle or its driver, such as an automated voicemessage, text message, message displayable at a mobile telephone by asoftware application installed therein, etc.; or any combination thereoffor example. By way of further example, a proximity sensor, beam (e.g.infra-red beam) detection system, or other detection means incombination with an indicator (e.g. electronic display), messagingsystem, etc., may act as a barrier for example. The barrier may be anyone or more of an entry barrier, exit barrier, and integrally connectedsingle barrier, for example.

In some embodiments, there is one stall barrier at each parking stallamong all or a portion of the parking stalls in the parking lot. In suchembodiments, one entry barrier and one exit barrier are integrallyconnected and overlapping to form each single stall barrier. Stallbarriers may be employed in addition or alternatively to entry and exitbarriers at the outer perimeter of the parking lot. In some embodimentsand parking lots, the stall barrier(s) associated with each given stallare the only entry and exit barriers of the parking lot.

Stall barriers are typically implemented by a moveable post or otheritem that is “opened” by retracting, rotating or otherwise moving thepost away from its obstruction position in order to permit parking inthe stall, remains “open” during the entire time that the vehicle isparked in the stall, and is typically “closed” after the vehicle hasvacated the parking stall by moving the stall barrier back into itsobstruction position to prevent further parking in the stall until thestall barrier is re-opened. The opening and closing movements of thestall barrier are automated under computerized control by the system 10.In general, any suitable type of barrier may be employed at a restrictedparking stall, such as a red/green light, electronic display or otherindicator, messaging system, other barrier, and any combination thereoffor example. By way of further example, a proximity sensor, beam (e.g.infra-red beam) detection system, or other detection means incombination with an indicator (e.g. electronic display), messagingsystem, etc., may act as a stall barrier.

In some embodiments, there is a plurality of entry and exit barrierssuch as entrance and exit gates. For example, some parking lots have oneentry barrier adjacent one exit barrier at each of a plurality of accesspoints along the outer perimeter of the parking lot. Additionally oralternatively, inside the parking lot there may be an interior entrybarrier adjacent an interior exit barrier for access to a restrictedsection of the parking lot. In some embodiments, there is a plurality ofinterior entry and exit barriers defining a plurality of restrictedsections of the parking lot. Each restricted section may be of anysuitable size ranging from a single parking stall to every stall in theparking lot. Interior barriers may be employed in addition oralternatively to each of the outer perimeter barriers and employed inaddition or alternatively to any number of stall barriers. In thedescription herein, the exterior side of an interior entry or exitbarrier is typically the side of the given interior barrier closer tothe outer perimeter of the parking lot, and the interior side of aninterior entry or exit barrier is intended to mean the side to whichaccess is restricted by the given interior barrier.

In general, any combination of any number of outer perimeter barriers,any number of interior barriers, and any number of stall barriers iswithin the scope contemplated by the present invention. If there arezero outer perimeter barriers, zero interior barriers, and zero stallbarriers, then the parking lot is an unrestricted-access parking lot.

Referring to FIG. 1, the system 10 is operable to communicate with asmart device 12. The smart device 12 can be any communications deviceoperable to send and receive communications, including telephonecommunications via a telephone network (not shown), data communicationssuch as machine-to-machine communications, other wireless or wiredcommunications, and any combination thereof for example. The smartdevice 12 is typically a mobile telephone, but in variations may be anygeneral purpose computer device, laptop computer, tablet computer,personal communication device, wearable technology device, automobile orother transportation vehicle (e.g. having installed thereincommunications equipment), similar computational device, or anycombination thereof for example. A smart device that is integrated intoa vehicle may be referred to as a smart vehicle. Communications betweenthe system 10 and the smart device 12 may be conducted directly, such asvia the direct link 14 shown in FIG. 1, or indirectly, such as via atelecommunications network, LAN (local-area network), WAN (wide-areanetwork), and/or a global communications network like the Internet 16shown in FIG. 1. In the first embodiment, the system 10 and the smartdevice 12 ordinarily communicate with each other via the direct link 14by near-field wireless communications (e.g. Bluetooth™ standardcommunications, NFC (Near-Field Communications) standard communications,etc.), but are operable to communicate via the Internet 16 as a backupmethod in case of failure to communicate via the direct link 14. In someembodiments, however, communications between the server 10 and the smartdevice 12 are conducted only via the direct link 14. In someembodiments, communications between the server 10 and the smart device12 are conducted only indirectly, such as via the Internet 16.Communication via an indirect link may be implemented using any suitabletelephone or other communications technology, for example. In general,communications between the system 10 and the smart device 12 may betransmitted via any wired or wireless connection, including a copperwire link, a coaxial cable link, a fiber-optic transmission link, aradio link, a cellular telephone link, a satellite link, a line-of-sightfree-optics link, and any combination thereof for example.

The system 10 includes a server 18, which may be any computing device(s)such as a general purpose computer, microcomputer, minicomputer,mainframe computer, distributed network for computing, functionallyequivalent discrete hardware components, etc., and any combinationthereof for example. In the first embodiment, the server 18 includes aprocessing circuit, such as a CPU (Central Processing Unit), forperforming programmable digital computations and a non-transitoryRead/Write memory for storing digital data. The Read/Write memory of theserver 18 may include any combination of volatile memory, such as RAM(Random Access Memory), and non-volatile memory, such as flash memory,universal serial bus (USB) connected memory units, magnetic storage,optical storage, magneto-optical storage, etc., and any combinationthereof for example. The Read/Write memory of the server 18 typicallyincludes data storage circuitry operable to store program code fordirecting operations of the processing circuit of the server 18.

In the first embodiment shown in FIG. 1, the server 18 is connected to anon-transitory database 20 for data storage. While FIG. 1 shows theserver 18 and the database 20 as being separate from each other, in someembodiments the database 20 forms an integral part of the Read/Writememory of the server 18. Additionally or alternatively to storing datain the database 20, the server 18 in the first embodiment is operable tostore data via the Internet 16 using the Internet-connected additionalresources 22.

Still referring to FIG. 1, the system 10 in the first embodimentincludes an entry controller 24 for controlling the entry barrier (notshown) and an exit controller 26 for controlling the exit barrier (notshown). In the first embodiment, the entry controller 24 and the exitcontroller 26 are operable to open and close the entry and exitbarriers, respectively, including in some embodiments being operable toopen and/or close the barrier(s) in response to commands received fromthe server 18. The controller 24 and 26 may be motor controllers, forexample.

In embodiments where the entry and exit barriers are integrallyconnected to each other to form a single barrier, such as a roll gate ora stall barrier, a single controller 24 or 26 may be suitably employedfor the single barrier.

Embodiments having a plurality of entry barriers and a plurality of exitbarriers, such as for parking lots having a plurality of restrictedsections, typically include a corresponding plurality of entrycontrollers 24 and a corresponding plurality of exit controllers 26,respectively. In some embodiments, however, a single controller 24 or 26may be operable to control a plurality of entry and/or exit barriers.

Each of the entry and exit controllers 24 and 26 are operable tocommunicate with the server 18 by any suitable technique, such as by adirect link as shown in FIG. 1 and/or via the Internet 16 as also shownin FIG. 1. Typically, the entry controller 24, the exit controller 26,both of the entry and exit controllers 24 and 26, or a single controller24 or 26 includes a non-transitory memory for storing data, such asmeasurement values and/or program code, and includes processingcircuitry, such as a CPU, for performing digital computations. In someembodiments (not shown), one or both of the entry controller 24 and theexit controller 26 form part of the server 18 such that the server 18 isoperable to directly control one or both of the entry barrier(s) and theexit barrier(s), respectively. While not shown in FIG. 1, in someembodiments some or all of the server 18 functions are performed by atleast one of the entry controller 24, exit controller 26 and singlecontroller, for example such that the server 18 shown in FIG. 1 formspart of the controller(s) 24 or 26.

The system 10 shown in FIG. 1 includes vehicle sensors 28, 30, 32 and34, each of which is operable to determine whether a vehicle is presentat a particular location associated with the parking lot such as at theexterior or interior side of the entrance gate or other entry barrier(not shown) or at the interior or exterior side of the exit gate orother exit barrier (not shown), for example. In the first embodimentshown in FIG. 1, the vehicle sensor 28 is operable to sense the presenceor absence of a vehicle at a vehicle entry location, which for typicalparking lots is commonly defined as being in the entry lane adjacent toand on the exterior side of the entry barrier. The vehicle sensor 28 inthe first embodiment is also operable to permit detection of thepresence or absence by at least one of the entry controller 24 and theserver 18. The vehicle sensor 30 is operable to sense the presence orabsence of a vehicle in the entry lane adjacent to and on the interiorside of the entry barrier, and is operable to permit detection of thepresence or absence by at least one of the entry controller 24 and theserver 18. The vehicle sensor 32 is operable to sense the presence orabsence of any vehicle at a vehicle exit location, which for typicalparking lots is commonly defined as being in the exit lane adjacent toand on the interior side of the exit barrier. The vehicle sensor 32 inthe first embodiment is also operable to permit detection of thepresence or absence by at least one of the exit controller 26 and theserver 18. Also, the vehicle sensor 34 is operable to sense the presenceor absence of a vehicle in the exit lane adjacent to and on the exteriorside of the exit barrier, and is operable to permit detection of thepresence or absence by at least one of the exit controller 26 and theserver 18. In the context of the exit barrier, any vehicle refers toeither the particular vehicle also sensed adjacent the entry barrier oranother vehicle different from that particular vehicle.

FIG. 1 shows two vehicle sensors 28 and 30 in communication with theentry controller 24 and two other vehicle sensors 32 and 34 incommunication with the exit controller 26. Additionally oralternatively, in some embodiments one or more vehicle sensors areoperable to communicate with the server 18, such as by communicatingdirectly (e.g. direct link 14) by wired or wireless communications forexample or indirectly via a LAN, WAN, other communications link, theInternet 16 or any combination thereof for example. In some embodiments,one or more of the vehicle sensors 28 to 34 form part of the server 18such that the server 18 is operable to directly sense the presence orabsence of a vehicle at specifiable location(s).

In some embodiments, one or more server 18 functions are distributedamong one or more of the server 18, entry controller 24, exit controller26, and one or more of the vehicle sensors 28 to 34 in any combinationfor example. In a distributed server architecture, communicationsbetween distributed server 18 components may be implemented in anysuitable manner, and may involve two-way communications for example.

In the first embodiment, on the basis of an indication of presence orabsence sensed by the vehicle sensor 28, the system 10 is operable todetermine whether a vehicle is present at the entrance gate, other entrybarrier, or otherwise in a position to enter into the parking lot,restricted section or parking stall. Also, on the basis of an indicationof presence or absence sensed by the vehicle sensor 30, the system 10 isoperable to determine whether a vehicle is present at the interior sideadjacent the entry barrier, such as after entering the parking lot bypassing by the opened entry barrier. Similarly, the system 10 isoperable to determine whether a vehicle is present at the exit gate,other exit barrier, or otherwise in a position to exit the parking lot,restricted section or parking stall on the basis of an indication ofpresence or absence sensed by the vehicle sensor 32. While a vehiclebeing in a position to exit the parking lot or restricted sectionthereof may be sensed by the presence of the vehicle at a vehicle exitlocation, the vehicle exiting a parking stall may be sensed by thechange from presence to absence at the parking stall, for example.Additionally, on the basis of an indication of presence or absencesensed by the vehicle sensor 34, the system 10 is operable to determinewhether a vehicle is present at the exterior side adjacent the exitbarrier, such as after exiting the parking lot by passing by the openedexit barrier. In general, any number of vehicle sensors may be employedat any suitable location(s) within or surrounding the parking lot. Forexample, one or more vehicle sensors may be employed at a given parkingstall, including having one vehicle sensor positioned at the givenparking stall itself and/or one or more vehicle sensors positionedadjacent the given parking stall along one or more access routes to andfrom the given parking stall, respectively.

In some embodiments, the server 18 in conjunction with the one or morevehicle sensors associated with a given parking stall implement a stallbarrier and its associated entry and/or exit controller(s) 24 and 26, asfurther described herein below.

Typically, each vehicle sensor 28 to 34 is implemented as an inductivesensor positioned underground at its desired location. Such inductivesensor may include loops of wire having a loop size commensurate withthat of a typical vehicle, in a manner known in the art. However, othervehicle sensing technologies are possible. Some examples include visualdetection by computerized image analysis of video data; infraredsensing; sonar/radar detection; the breaking of a laser or other beam;mechanical detection such as by ground-level pressure sensors,ground-level switches, above-ground switches for making contact as avehicle passes by, other mechanical sensors; chemical detection; otheranalogous detection techniques; and any combination thereof for example.

Still referring to FIG. 1, the system 10 in the first embodiment isoperable to determine the location of the smart device 12 when the smartdevice 12 is in the vicinity of at least one of the entry barrier, exitbarrier and single, combined barrier. In some embodiments, the system 10is operable to determine the location of the smart device 12 whenever itis located at the parking lot, including in some cases being anywherewithin the parking lot.

In the first embodiment, the system 10 includes one or more locationbeacons such as the entry beacon 35 and the exit beacon 36 shown inFIG. 1. Each beacon 35 and 36 is operable to broadcast a wireless signal37 that can be received by the smart device 12 when the smart device 12is located within the broadcast range of the beacon 35 and/or 36.Typically, the beacons 35 and 36 are operable to broadcast theirwireless signals 37 in accordance with a near-field wirelesscommunications standard such as Bluetooth™, NFC (Near-FieldCommunications), similar communications standard, and any combinationthereof for example. The beacons 35 and 36 broadcast their wirelesssignals 37 within a limited range that is in some embodiments adjustableaccording to desired preferences. Any number of entry beacons 35 and anynumber of exit beacons 36 may be employed in any combination. By way ofexample only, a first entry beacon 35 may be deployed outside theparking lot in the vicinity of the entry barrier, a second entry beacon35 may be deployed at the entry lane adjacent to and on the exteriorside of the entry barrier, and a third entry beacon 35 may be deployedat the entry lane adjacent to and on the interior side of the entrybarrier, for example. Similarly, a first exit beacon 36 may be deployedinside the parking lot in the vicinity of the exit barrier, a secondexit beacon 36 may be deployed at the exit lane adjacent to and on theinterior side of the exit barrier, and a third exit beacon 36 may bedeployed at the exit lane adjacent to and on the exterior side of theexit barrier, for example.

In the first embodiment, the wireless signal 37 includes anidentification code identifying the particular beacon that isbroadcasting that wireless signal 37. For example, the entry beacon 35may broadcast its identification as the code “35” while the exit beacon36 may broadcast its identification as the code “36”.

In the first embodiment, the smart device 12 has installed therein asoftware application program that is compatible with the system 10. Thesmart device 12 application renders the smart device 12 operable toreceive the wireless signals 37 from a given beacon 35 or 36; parse fromthe received wireless signal 37 the identification code associated withthe given beacon 35 or 36; determine on the basis of signalcharacteristics (e.g. propagation time and/or signal 37 strength decay)the distance between the smart device 12 and the given beacon 36 or 37;and communicate to the server 18 the received identification code,determined distance, and an identification of the smart device 12. Inthe first embodiment, the server 18 is operable to receive thecommunication from the smart device 12; parse from the communication thebeacon identification, associated distance, and smart device 12identification; determine the location of the given beacon 35 or 36 inresponse to the beacon identification (such as by lookup table); andthereby determine a current location associated with the identifiedsmart device 12. Where the smart device 12 receives multiple broadcastsfrom multiple beacons 35 and/or 36 and the smart device 12 is operableto determine the distance between itself and each of the multiplebeacons 35 and/or 36, the server 18 in some embodiments is operable todetermine by known trilateration techniques a more accuratedetermination of the smart device 12 location. While in the firstembodiment, the smart device 12 is operable to determine the distancebetween the smart device 12 and the given beacon 35 or 36, in avariation the smart device 12 does not determine its distance from givenbeacon 35 and only communicates to the server 18 the receivedidentification code and the smart device 12 identification, such thatthe server 18 is operable to determine the location of the smart device12 within an accuracy commensurate with the wireless range of the givenbeacon 35 or 36. In all such variations, the system 10 is advantageouslyoperable to determine the current location of the smart device 12without requiring that the smart device 12 itself determine its owncurrent location and without requiring that the smart device 12determine or otherwise obtain the location of any beacon 35 or 36.

In some embodiments, one or more location sensors are implemented asenhanced variations of the beacons 35 and 36. In some instances, suchlocation sensors are operable to perform two-way wireless communicationswith the smart device 12. In such embodiments, the smart device 12 andthe location sensor typically communicate via near-field wirelesscommunications, such as by Bluetooth™ standard communications, NFC(Near-Field Communications, similar communications standard, anycombination thereof for example. In such embodiments, the locationsensor may include three or more wireless communications devices (notshown) spaced apart from each other that, together, are operable todetermine the location of the smart device 12 by trilateration of one ormore communications transmitted between the smart device 12 and thedifferent wireless communications devices. In variations of suchembodiments, the location sensor may include one or more sets ofwireless communications devices such that each set is operable todetermine the location of the smart device 12 when it is in the vicinityof one entry barrier, in the vicinity of one exit barrier, in thevicinity of a pair of entry and exit barriers, or in the vicinity of aplurality of entry and/or exit barriers. In some embodiments at some orall parking lots, the location sensor is operable to determine thelocation of the smart device 12 whenever it is in the vicinity of theparking lot. Such wireless communications devices can be near-fieldwireless communications devices, for example.

In some embodiments, each wireless communications device of the locationsensor includes a non-transitory memory for storing data, such asmeasurement data and/or program data, and includes processing circuitry,such as a CPU, for performing digital computations.

In some embodiments in which the location sensor is implemented as anenhanced variation of the beacons 35 and 36, the location sensorincludes a number of proximity sensors (not shown) disposed at theparking lot. For example, one proximity sensor may be disposed at theentry lane on the exterior side of the entry barrier, and anotherproximity sensor may be disposed at the exit lane on the interior sideof the exit barrier. In use, the smart device 12 may be held insufficiently close proximity to a given proximity sensor for the givenproximity sensor to register the location of the smart device 12, suchas while the smart device 12 is in communication with the server 18 soas to facilitate the server 18 in associating the smart device 12identification with proximity sensing of the smart device 12 todetermine its location.

In some embodiments in which the location sensor is implemented as anenhanced variation of the beacons 35 and 36, the location sensorincludes a number of NFC (Near-Field Communication) devices (not shown)disposed at the parking lot. For example, one NFC device may be disposedat the entry lane on the exterior side of the entry barrier, and anotherNFC device may be disposed at the exit lane on the interior side of theexit barrier. In use, the smart device 12 may be held in sufficientlyclose proximity to a given NFC device for the given NFC device toestablish near field communications with the smart device 12 (e.g. undercontrol of the application program installed therein in accordance withthe present invention) so as to allow the NFC device to receive thesmart device 12 identification and also determine the location of thesmart device as being proximate to the given NFC device.

Other technology for implementing the location sensor is possible, andany suitable location sensor or combination of location sensors may beemployed to determine the location of the smart device 12 withoutrequiring that the smart device 12 determine its own location.

The location sensor in some such embodiments is operable to communicatevia any suitable communications technology with the server 18.Additionally or alternatively, such as possibly in the manner of anoptional backup method, the location sensor in some embodiments isoperable to communicate via any suitable communications technology withthe entry and exit controllers 24 and 26, which in turn are operable tocommunicate with the server 18. Other communications schemes arepossible for any given location sensor.

In some embodiments, one or more location sensors, or any wirelesscommunications device thereof, forms part of the server 18 such that theserver 18 is operable to directly communicate with the smart device 12to determine the identification and/or location of the smart device 12.In some embodiments, the server 18 is operable to perform the operationsof one or more near-field wireless communications devices, proximitysensors, and/or NFC devices of such location sensors. The server 18implements any suitable rules regarding the boundaries within which thesmart device 12 must be located to be considered at an entry or exitlocation and the boundaries within which a vehicle must be located to beconsidered at the same entry or exit location, respectively. In manycases, a smart device 12 will be inside a vehicle that is present at anentry or exit location. However, this need not always be the case andthe boundaries of the entry and exit locations may exceed those of thevehicle entry and vehicle exit locations, respectively, for example.Typically, the defined vehicle entry and vehicle exit locations at leastoverlap with their associated entry and exit locations, respectively,and may lie entirely within the boundaries of their associated entry andexit locations, respectively, for example.

Exemplary Signal Timeline

Referring to FIGS. 1 and 2, a typical exemplary parking scenarioinvolving the first embodiment of the invention begins with the smartdevice 12 optionally communicating a request for parking lot informationto the server 18, which receives the parking lot information request.The server 18 is typically operable to obtain, such as by retrievingfrom the database 20, information concerning each parking lot where aperson may park their vehicle in accordance with embodiments of theinvention. For each such parking lot, its associated information mayinclude the location (e.g. street address) of the parking lot, parkinglot hours of operation, pricing information, payment information,special event parking information, instructions or other guidance formaking parking reservations at the parking lot, parking lot rules ofconduct, other related information or any combination thereof, forexample. In cases where the present invention has been implemented inmultiple parking lots in a given city, country or around the world, theserver 18 may be operable to use the location of the smart device 12 toprovide parking lot information that is geographically close to thecurrent location of the smart device 12. Additionally or alternatively,the server 18 may communicate all available parking lot information, inwhich case the smart device 12 may be operable to filter the receivedinformation based on defined relevance to the smart device 12 user.Typically, the smart device 12 does not need to be in the vicinity of asuitable parking lot to request or receive the parking lot information;and the communications between the smart device 12 and the server 18related to the parking lot information can be implemented by anysuitable techniques, such as ordinary mobile telephone communicationstechniques for example.

After the server 18 has communicated the parking lot information to therequesting smart device 12, the smart device 12 presents theinformation, or a subset thereof, to the user, such as by displaying astreet map with suitable parking lots marked thereon. In someembodiments, the smart device 12 is operable to provide drivingdirections from the current location of the smart device 12 to aselected parking lot. Typically, the smart device 12 requests theparking lot information in response to user input (e.g. requesting a mapdisplay). Also, current parking lot information may be included with aninitial download from the server 18 of the smart device 12 application,for example. Updated parking lot information may be provided at eachuser request of the parking lot information, by automatic or manuallyselected downloads of updates, or any combination thereof for example.

In some embodiments, the parking lot information is not available, or isoptionally provided. Additionally or alternatively, the map displayfeature may not be available to every smart device 12 in allembodiments, or may be optionally provided.

In the first embodiment, the entry beacon 35 broadcasts its entryidentification code. When the smart device 12 arrives in the vicinity ofthe parking lot where it is within the wireless range of the entrybeacon 35, the smart device receives the entry beacon identification andis operable to communicate an entry request to the server 18. In thefirst embodiment, the entry request contains the entry beacon 35identification and also identifies the requesting smart device 12 in amanner associated with the entry beacon 35 identification.

In variations, user input may or may not be required to generate theentry request. For example, the smart device 12 application typicallyallows the smart device 12 user to pre-register with the system 10 toprovide persistent or recurring information such as personalinformation, payment preferences, and the like. In this manner, thesmart device 12 is operable to generate the entry request withoutre-entry of such persistent information each time the smart device 12user wishes to park their vehicle (not shown). For example, the smartdevice 12 application can be programmed to present to the smart device12 user a single “OK” or “ENTER” button to be pressed when the smartdevice 12 is in the vicinity of the parking lot. The “OK” or “ENTER”button may be a soft button displayed on a touchscreen, a keypad hardbutton, or other button of the smart device 12 for example. When the“OK” or “ENTER” button is pressed by the smart device 12 user when thesmart device 12 is in the vicinity of the parking lot and its entrybeacon 35, then the smart device 12 generates the entry request inresponse to user input consisting solely of no more than the singlepress of the “OK” or “ENTER” button. In general, any suitable form ofuser input may be employed as a user command, such as a voice command,biometric input such as a fingerprint reading, a visually detectableuser gesture, other user input, or any combination thereof for example.Accordingly, in some embodiments the entry request is generated by thesmart device in response to the smart device receiving no more than asingle user command. In some embodiments, the smart device 12application may be programmed to automatically transmit the entryrequest, absent any user input, whenever the smart device 12 determinesthat it is in the vicinity of the parking lot, such as by receiving theentry beacon identification for example.

In some embodiments, pre-registration with the system 10 may be fully orpartly completed online via a website associated with the system 10, forexample.

In the first embodiment, the entry request generated by the smart device12 includes an identification of the smart device 12, such as byincluding the mobile telephone number of the smart device 12. Ingeneral, the smart device 12 and/or its user may be identified orotherwise associated with each other in any suitable manner, such thatthe smart device 12 identification may be or include a hardware deviceidentification of the smart device 12; a software identificationassociated with installed software of the smart device 12; a telephonenumber associated with the smart device 12; an Internet protocoladdress, URL (Uniform Resource Locator) or other communicationsidentification associated with the smart device 12; a useridentification such as a user name; an officially issued useridentification such as a birth certificate number, social insurance orwelfare number, government ID, etc.; an image of an officially issuedidentification certificate; driver's licence number; a vehicle licenceplate number; an image of a licence plate; a vehicle registrationnumber; a vehicle identification number (VIN) or other vehicleidentification code, such as in the case of a smart vehicle for example;a financial card number such as a credit or debit card number; otherrelated identification; or any combination thereof for example.Additionally or alternatively, the identification of the smart device 12can be transmitted from the smart device 12 to the server 18 in aseparate communication from the entry request. Other communicationsbetween the smart device 12 and the server 18 are possible and arewithin the scope contemplated by the present invention, such as furtheruser input prompts for example. In some embodiments, the server 18 isoperable to query an additional resource 22 to obtain and/or verify thesmart device 12 identification.

While FIG. 2 shows an exemplary scenario involving the first embodimenthaving beacons 35 and 36, in some embodiments a given parking lot mayinclude one or more location sensors (implemented as enhanced variationsof the beacons 35 and 36) operable to determine the location of thesmart device 12, such as in response to two-way communications betweenthe smart device 12 and the location sensor(s). For example, thelocation sensor(s) may be operable to calculate the location of thesmart device 12 by trilateration of communications between the smartdevice 12 and wireless communications devices (not shown) of thelocation sensor(s). In such embodiments, the smart device 12 maytransmit to the location sensor(s) an entry request containing the smartdevice 12 identification. Thereafter, the location sensor(s) determinethe location of the smart device 12, and then transmit the smart device12 identification and the smart device 12 location to the server 18, orto the entry controller 24 which forwards them to the server 12.Additionally or alternatively, the location sensor(s) and/or entrycontroller 24 may include server 18 functionality such that the locationsensor(s) and/or entry controller 24 further process the smart device 12identification and smart device 12 location.

Using the smart device 12 identification, the server 18 queries thedatabase 20 for the current status associated with that smart device 12identification, and retrieves the current status from the database 20.In the exemplary scenario of FIG. 2, the status is based on informationassociated with the smart device 12 identification, such aspre-registration information previously provided by the smart device 12user when opening a user account with the system 10 and any subsequentupdates thereto.

For the scenario in which the smart device 12 is not pre-registered withthe system 10 and no status exists in the database 20 in associationwith the smart device 12 identification, the system 10 will reject entryin some embodiments such that the entry barrier does not open.Alternatively, in some embodiments the system 10 permits entry to anunidentified smart device 12 and continues communicating with the smartdevice 12 to obtain the necessary information for registering the smartdevice 12 and/or processing a parking payment after entry. Similarly, insome embodiments the system 10 rejects entry if the status indicatesthat the smart device 12 is not in compliance with payment requirementsof the system 10, such as by being in arrears regarding previous parkingfees, while in some embodiments the system 10 permits entry even if thesmart device 12 identification is associated with payment arrears.Additionally or alternatively, the system 10 in some embodiments issuesan alert to a human attendant who can arrive at the location to assist.In the context of rejecting entry, other alerts that are issued by thesystem 10 in variations of embodiments include alerts to the smartdevice 12 user, alerts to humans in a call center or other establishmentof the parking lot business, and alerts to initiate parking enforcementagainst the vehicle associated with the smart device 12 and/or againstthe smart device 12 user, for example.

In some embodiments, parking reservations are offered at some or allparking lots. A parking reservation provides a measure of assurance ofthe availability of parking at a given parking lot, and may specifyavailability at a particular parking stall at the given parking lot forexample. In one instance, the smart device 12 may communicate to theserver 18, at any time prior to actually parking, a request for aparking reservation. The server 18 in the first embodiment is operableto query the database 20 for availability and subsequently confirm ordeny the parking reservation, such as in a reply communication to thesmart device 12. The application program installed in the smart device12 may provide further user features such as integrating the parkingreservation into a calendar system, etc. Typically before communicatingconfirmation of a parking reservation, the server 18 creates the parkingreservation by updating the database 20, which may include associatingthe parking reservation in the database 20 with the smart device 12identification for example. Additionally or alternatively to directcommunications between the smart device 12 and the server 18, athird-party computerized parking reservation system (shown in FIG. 1 asan additional resource 22) may be employed. In such instance, theparking reservation system communicates a request for a parkingreservation to the server 18, which then confirms or deniesavailability, such as by a reply communication from the server 18 to thethird-party parking reservation system. The server 18 may create theparking reservation by creating an association in the database 20between the parking reservation and the smart device 12 identification,a particular identification specified by the third-party parkingreservation system, other identifying means, and any combination thereoffor example. In some embodiments, parking reservations are offered via awebsite interface, which may be a third-party operated website forexample, and communications with the server 18 are effected via theInternet 16. In some embodiments, the third-party parking reservationsystem is provided with direct access to the database 20, and parkingreservations are created by the third-party parking reservation system.Additionally or alternatively, the server 18 may be operable tocommunicate specifiable database 20 contents to the third-party parkingreservation system such that the third-party parking reservation systemis operable to create a parking reservation, which may be an offlineparking reservation for example.

In some embodiments, the server 18 is operable to communicate a parkingreservation status or other notification to one or both of the smartdevice 12 and a third-party computerized system (shown in FIG. 1 as anadditional resource 22), which may be a third-party parking reservationsystem. Such notification may include a reminder that a monthly (orother periodic) payment is due soon; notice that a payment is now due;notice that a payment is overdue; notice of a penalty of any kind;notice of a fee reduction; notice of a fee reimbursement (e.g. by athird-party business); notice of elimination of a fee (e.g. bypromotional offer); a reminder that a parking reservation that is comingsoon remains valid; notice that a parking reservation will expire soon;notice that a parking reservation has expired; notice that a reserved orunreserved parking session will expire soon; notice that a reserved orunreserved parking session has expired; notice that a reserved orunreserved parking session has begun (e.g. to the smart device 12 and/ora nearby business); notice to the smart device 12 and/or third-partycomputerized system that a reserved or unreserved parking session hasended (e.g. upon vacating a parking stall and/or the parking lot);notice of a parking status; other notifications; and any combinationthereof for example. Notifications may be communicated by the server 18by text message (e.g. MMS, SMS, etc.), e-mail, automated voice call,telecommunication, machine-to-machine communications, othercommunication protocols or schemes, and any combination thereof forexample. Notifications to the smart device 12 may involve executing bythe smart device 12 functions of the application program installedtherein in accordance with the present invention. Notices of parkingstatus includes in some embodiments transmitting by the server 18 aparking status to a third-party parking enforcement agency (shown inFIG. 1 as an additional resource 22). For example, a list of expirationsmay include future dates and times of upcoming expirations and/or pastdates and times of now expired statuses may be transmitted. Such listmay be associated with particular parking stalls, an entire parking lot,particular smart device 12 identifications, particular vehicles, etc.,so as to facilitate predictive patrolling. To associate a parking statuswith a particular vehicle, the database 20 may include, in associationwith a given smart device 12 identification, a vehicle identification(e.g. licence plate number), which may have been entered into thedatabase 20 in response to user input received from the smart device 12during registration, for example.

In the first embodiment, the server 18 is operable to query the database20, search a lookup table, or otherwise determine a location associatedwith the entry beacon 35 identification. By way of examples, the server18 in variations of embodiments is operable to determine the location ofthe smart device 12 by associating the entry beacon 35 identificationreceived from the smart device 12 with a particular entry beacon 35installed at a particular location or parking lot, with a particularentry controller 24 installed at a particular location or parking lot,with a particular entry barrier in proximity to the identifiable entrybeacon 35, with a particular parking stall or restricted section inproximity to the identifiable entry beacon 35, other associations, andany combination thereof for example.

In the first embodiment, the server 18 transmits to the entry controller24 a command to open the entry barrier if the smart device is determinedby the server 18 to be at an entry location (such as being located atthe entry lane on the exterior side of the entry barrier, for example)and the status associated with the smart device 12 identification isindicating there is no entry rejection of the smart device 12.

In the exemplary scenario of FIG. 2, after the entry controller 24receives the open-barrier command, the entry controller 24 receives anindication as to whether a vehicle is present at the entry location(e.g. at the entry lane on an exterior side of the entry barrier). Inthe exemplary embodiment shown in FIG. 1, the presence of a vehiclelocated at the vehicle entry location is sensed by the vehicle sensor28. Typically, the entry controller 24 controls the vehicle sensors 28and 30 to track the location of the vehicle as it passes by the entrybarrier.

In some embodiments, however, the server 18 issues a command to theentry controller 24 to determine whether a vehicle is present at thevehicle entry location; the entry controller 24 controls its associatedvehicle sensor 28 to obtain the presence indication; the entrycontroller 24 transmits the presence indication to the server 18; andthen the server 18 transmits the open-barrier command to the entrycontroller 24 if the entry beacon 35 identification is associated withthe particular entry controller 24, the presence indication confirmsthat a vehicle is present at the vehicle entry location, and the statusassociated with the smart device 12 identification is indicating thereis no entry rejection of the smart device 12. In variations, the server18 may issue the command to the entry controller 24 to determine whethera vehicle is present at one or more vehicle entry locations at any timeafter the server 18 receives the entry request for example.

In some embodiments, one or more of the vehicle sensors 28 to 34 arecontinuously monitoring for the presence of a vehicle at theirrespective locations and continuously transmitting indications ofpresence or absence. In the exemplary scenario of FIGS. 1 and 2, thesmart device 12, the smart device 12 user, and the user's vehicle arrivein front of the entrance gate at approximately the same time. Inembodiments in which the vehicle sensor 28 is continuously monitoringfor the presence of vehicles, the vehicle sensor 28 is transmitting thepresence indication at approximately the same time as the smart device12 is receiving the entry beacon 35 identification. Thus, the server 18is receiving the entry request at approximately the same time as thevehicle presence is being detected and transmitted to the server 18(e.g. directly and/or via the entry controller 24). The server 18 isthereafter operable to determine whether to issue an open-barriercommand to the entry controller 24 on the basis of the entry beacon 35identification, the vehicle presence and the status associated with thesmart device 12. In general, the system 10 is operable to determinewhether the entry location of the smart device 12 and the vehicle entrylocation are associated locations (e.g. both at the entry lane on anexterior side of the entry barrier).

After the system 10 determines that the entry barrier should be opened,the entry controller 24 opens the entry barrier, thereby permitting thevehicle to enter the parking lot. When the vehicle has moved forwardfrom the exterior side of the entry barrier to the interior side of theentry barrier, the vehicle sensor 28 then senses the absence of avehicle (in the exemplary scenario where another vehicle does notimmediately fill the vacant position in front of the entry barrier).Also, the vehicle sensor 30 senses the presence of a vehicle when itarrives at the interior side of the entry lane adjacent the entrybarrier, and the entry controller 24 closes the entry barrier.

In the first embodiment, the server 18 is operable to override theordinary operation of the entry controller 24 and issue a command forthe entry controller 24 to close the entry barrier. In some embodiments,the entry controller 24 does not close the entry barrier until receivinga close-barrier command from the server 18. In some embodiments,indications of the presence and/or absence sensed by the vehicle sensor30 are transmitted to the server 18, which transmits a command to theentry controller 24 to close the entry barrier.

When the server 18 becomes aware that the entry barrier has been openedand then closed, such as by receiving an entry-barrier status from theentry controller 24 as shown in FIG. 2, the server 18 is operable tostore an updated count of the number of vehicles that have entered theparking lot through the entry barrier. In the first embodiment, theserver 18 is also operable to store the time at which the entryoccurred, for subsequent use in calculating a parking fee based on theduration time spent parking. Typically, the count of vehicles that haveentered the parking lot (or other related quantities, such as lotoccupancy) and the time-stamps are stored by the server 18 in thedatabase 20.

As shown in FIG. 2, the server 18 is operable to interact withthird-party systems (shown in FIG. 1 as additional resources 22), suchas by notifying selected third parties, if any, of the entry associatedwith the smart device 12 identification. In the first embodiment, theserver 18 is operable to permit the smart device 12 user to specify anumber of local businesses to be notified when the smart device 12 userarrives at the parking lot. For example, the smart device 12 user mayselect a local cafe to be automatically alerted on specifiable days(e.g. weekdays only, etc.) of their arrival at the parking lot, suchthat the cafe is able to prepare a specific beverage and food order tobe ready as soon as the smart device 12 user arrives on foot at thecafe. In the first embodiment, the server 18 is operable to store a listof participating businesses or other third-party entities from which thesmart device 12 user may select to receive notifications. Such list ofparticipating entities may be restricted geographically to nearbylocations, for example. By way of further examples, the server 18 may beoperable to transmit a notification to a third-party reservation system(e.g. “The reservation is fulfilled.”); to the user (e.g. “Yourreservation has begun.”); to a third-party parking management system(e.g. “Our lot is 96% full.”); potential users such as individuals innearby vehicles (e.g. “We have 30 parking stalls available.”);third-party sales systems (e.g. “We have 20 parking stalls available ata time-limited discounted price.”); other notification recipients; andany combination thereof for example. Notification may be performed byany suitable communications technology, such as via the Internet 16 forexample. The notification feature is an optional feature and need not beimplemented in all embodiments.

For parking lots having a plurality of restricted sections, the statusassociated with a smart device 12 identification preferably indicatesentry and exit acceptances and rejections in respect of each of theplurality of restricted sections. After entering a first section, entryinto a second section may proceed in a manner analogous to entry intothe first section. In some embodiments, no further user input isrequired for access to further restricted sections to which the smartdevice 12 user has access in accordance with their status. In suchembodiments, the system 10 may include any number of beacons 35 and/or36, or any number of other location sensors (implemented as enhancedvariations of the beacons 35 and/or 36), and is operable to determinethe location of the smart device 12 as it approaches a further entrybarrier, or possibly a stall barrier, without requiring further userinput into the smart device 12. Upon determining that the smart device12 is near or adjacent the further entry barrier or stall barrier, upondetermining that a vehicle is present at such further entry barrier orstall barrier, and upon determining that the status associated with thesmart device 12 identification indicates there is no entry rejection ofthe smart device 12 to the further entry barrier or stall barrier, thenthe system 10 is operable in such embodiments to open the further entrybarrier or stall barrier.

In embodiments in which the server 18 in conjunction with the one ormore vehicle sensors associated with a given parking stall implement astall barrier and its associated entry and/or exit controller(s) 24 and26, one or more beacons or other location sensors associated with thegiven stall are employed to determine the smart device 12 location. Inthis manner, the server 18 is operable to determine whether the entrylocation of the smart device 12 and the vehicle entry location areassociated locations (e.g. both at the given stall at the time ofentering the given stall) and whether the exit location of the smartdevice 12 and the vehicle exit location are associated locations (e.g.both at the given stall at the time of exiting the given stall).

Referring to FIGS. 1 and 3, the exemplary parking scenario involving thefirst embodiment of the invention continues, at the conclusion of aparking session, with the smart device 12 receiving an exit beacon 36identification from an exit beacon 36 of the parking lot. Any givenparking lot may include any number of location beacons 35 and 36,including separate entry and exit beacons 35 and 36 for example. In someembodiments, the exit beacon 36 and the entry beacon 35 are the samebeacon located at that entry/exit location and having only one uniquebeacon identification. In some embodiments, there are multiple entrybeacons 35 and/or multiple exit beacons 36. Preferably, each separatebeacon has its own unique beacon identification. In the exemplaryscenario, the smart device 12 communicates an exit request to the server18, which receives that exit request.

In the first embodiment, the server 12 determines the identification andlocation of the smart device 12 on the basis of the received exitrequest and any other accompanying communications between the smartdevice 12 and the server 18. In the first embodiment, the server 18determines the location of the smart device 12 by look-up table (e.g. indatabase 20) so as to associate the exit beacon 36 identification with aspecific location (e.g. with a particular exit controller 26 operable tocontrol a particular exit barrier at that specific location), such thatthe smart device 12 becomes known to the server 18 to be at an exitlocation (e.g. the exit lane on the interior side of the entry barrier).

While FIG. 3 shows an exemplary scenario involving the first embodimenthaving beacons 35 and 36, in some embodiments a given parking lot mayinclude one or more location sensors (implemented as enhanced variationsof the beacons 35 and 36) operable to determine the location of thesmart device 12 in response to two-way communications between the smartdevice 12 and the location sensor(s), such as by trilateration or othertechniques in which the location sensor(s) calculate or otherwisedetermine the smart device 12 location. In such embodiments, the smartdevice 12 may transmit an exit request to the location sensor(s)containing the smart device 12 identification. Thereafter, the locationsensor(s) determine the location of the smart device 12, and thentransmit the smart device 12 identification and the smart device 12location to the server 18, or to the exit controller 26 which forwardsthem to the server 12. Additionally or alternatively, the locationsensor(s) and/or exit controller 26 may include server 18 functionalitysuch that the location sensor(s) and/or exit controller 26 furtherprocess the smart device 12 identification and smart device 12 location.

Using the smart device 12 identification, the server 18 queries thedatabase 20 for the current status associated with that smart device 12identification, and retrieves the current status from the database 20.

In the exemplary scenario of FIG. 3, the server 18 in the firstembodiment also calculates a parking fee on the basis of a parking rateassociated with the smart device 12 identification and the duration oftime spent parking. In general, the parking rate may vary with differentsmart device 12 identifications due to different smart device 12 userspurchasing different parking services. For example, some smart device 12users are willing to pay a higher parking rate to park at a moreconvenient parking stall of a given parking lot, while other smartdevice 12 users may be willing to park at a less convenient parkingstall of the given parking lot in order to receive a lower parking rate.Thus, in some embodiments the server 18 is operable to select anapplicable parking rate from a plurality of parking rates associatedwith the parking lot. In some embodiments, however, the same parkingrate is applied regardless of the smart device 12 identification suchthat the server 18 calculates the parking fee on the basis of factorsother than the smart device 12 identification. In some embodiments, theserver 18 receives the parking rate from an additional resource 22 (FIG.1).

In the first embodiment, the server 12 is operable to calculate theparking fee on the basis of a known parking rate multiplied by theduration of time spent parking. Such duration of time is determined bythe server 18 as the difference between the time at which an exitassociated with a smart device 12 identification from a parking stall,restricted section or the parking lot is occurring and the time at whichthe corresponding entry associated with the same smart device 12identification occurred. For example, the parking rate may be $3 perhour and the parking duration 78 minutes, in which case the parking feewould be $3.90. Other calculations of a parking fee are possible, suchas $6.00 in this example if the parking duration is quantized by thehour rather than by the minute, for example. In general, any suitableparking fee calculation scheme may be employed.

In a variation, the parking fee may be determined solely on the basis ofthe smart device 12 identification, such as in the case of a parkingsubscription in which a smart device 12 user pays periodically (e.g.monthly) for time-unlimited parking at the parking lot. Subscriptionparking may involve restrictions as to which parking stall or stalls areavailable, time-of-day restrictions (e.g. during regular working hoursonly), etc. In the case of subscription parking, payment typically doesnot coincide with parking lot exits as shown in the exemplary scenarioof FIG. 3. For example, payment processing for a monthly subscriptionmay occur automatically at the first day of each month, for example. Byway of further example, payment processing for an “all-day” parkingpermit may occur when the vehicle associated with a smart device 12 isentering the parking lot at the beginning of the all-day parkingsession. In general, the server 18 is operable in various embodiments tocalculate and/or collect the parking fee at any time before, during, orafter a given parking session.

In the exemplary scenario of FIG. 3, the server 18 transmits thecalculated time-based parking fee (e.g. $3.90) to the smart device 12,which displays the calculated parking fee to the user in the form of afee prompt (e.g. “Do you accept the charge of $3.90?”), and an OK buttonfor the smart device 12 user to accept payment processing of the parkingfee in accordance with pre-registered payment preferences andinformation associated with the smart device 12 identification. In avariation, pre-registered payment preference(s), if any, may beoverridden at the time by the user such that payment processing occursin response to a payment method and/or other payment preference(s)specified by the user after the display of the calculated parking fee.In variations, any suitable user input format may be employed for the OKbutton (e.g. voice command, biometric input, a visually detectable usergesture, other user input, or any combination thereof for example).Additionally, the smart device 12 in the exemplary embodiment alsodisplays a Cancel button (or similar) for the smart device 12 user toreject the displayed charge. In various embodiments, rejection by thesmart device 12 user may result in the server 18 issuing an alert for ahuman attendant to assist the smart device 12 user, initiation of atelephone call between the smart device 12 and a telephone associatedwith the parking lot (e.g. call center), opening an informationalwebpage in a browser of the smart device 12, a failure of the exitbarrier to open, other error handling procedures, or any combinationthereof for example. In some embodiments, a Cancel option is notprovided.

In the exemplary scenario of FIG. 3, the smart device 12 user pressesthe OK button such that the smart device 12 transmits an OK signal tothe server 18. Upon receiving the OK signal, the server 18 initiatespayment processing. Any suitable payment processing technique is withinthe scope contemplated by the present invention, including processing bya third-party payment processing service accessible as an additionalresource 22 for example.

In the exemplary scenario of FIG. 3, the system 10 had determined thelocation of the smart device 12 is at the exit location, and the statusassociated with the smart device 12 identification indicates there is noexit rejection of the smart device 12. In the first embodiment, theserver 18 accordingly transmits an open-barrier command to the exitcontroller 26, which receives the open-barrier command.

In the exemplary scenario of FIG. 3, after the exit controller 26receives the open-barrier command, the exit controller 26 receives anindication as to whether a vehicle is present at the vehicle exitlocation. In the exemplary embodiment shown in FIG. 1, the presence of avehicle located at the vehicle exit location is sensed by the vehiclesensor 32. Typically, the exit controller 26 controls the vehiclesensors 32 and 34 to track the location of the vehicle as it passes bythe exit barrier during its departure from the parking lot.

In some embodiments, however, the server 18 issues a command to the exitcontroller 26 to determine whether a vehicle is present at the vehicleexit location; the exit controller 26 controls its associated vehiclesensor 32 to obtain the presence indication; the exit controller 26transmits the presence indication to the server 18; and then the server18 transmits the open-barrier command to the exit controller 26 if theexit beacon 36 identification is associated with the particular exitcontroller 26, the presence indication confirms that a vehicle ispresent at the vehicle exit location, and the status associated with thesmart device 12 identification indicates there is no exit rejection ofthe smart device 12. In variations, the server 18 may issue the commandto the exit controller 26 to determine whether a vehicle is present atthe vehicle exit location at any time after the server 18 receives theexit request for example.

In some embodiments, one or more of the vehicle sensors 28 to 34 arecontinuously monitoring for the presence of a vehicle at theirrespective locations and continuously transmitting indications ofpresence or absence. In the exemplary scenario of FIGS. 1 and 3, thesmart device 12, the smart device 12 user, and the user's vehicle arriveat the exit barrier on its interior side at approximately the same time.In embodiments in which the vehicle sensor 32 is continuously monitoringfor the presence of vehicles, the vehicle sensor 32 is transmitting thepresence indication at approximately the same time as the smart device12 is receiving the exit beacon 36 identification. Thus, the server 18is receiving the exit request at approximately the same time as thevehicle presence is being detected. In embodiments in which the exitcontroller 26 transmits the presence indication to the server 18, theserver 18 is thereafter operable to determine whether to issue anopen-barrier command to the exit controller 26 on the basis of the exitbeacon 36 identification, the vehicle presence and the status associatedwith the smart device 12.

In general, the system 10 is operable to determine whether the exitlocation of the smart device 12 and the vehicle exit location areassociated locations (e.g. both at the exit lane on an interior side ofthe exit barrier).

In the first embodiment, the system 10 opens the exit barrier regardlessof the identity of the vehicle itself, provided the smart device 12 isidentified, located appropriately, has an appropriate associated status,and any vehicle is present at the vehicle exit location. However, insome embodiments, a vehicle identification is obtained by any suitablescheme such that the system 10 will not open the exit barrier unless thevehicle at the vehicle exit location, when a given smart device 12 withappropriate status is also at the associated exit location, is the samevehicle that entered when the smart device 12 had previously requestedentry or otherwise entered. Additionally or alternatively in suchembodiments, other error handling operations may be performed if thevehicle identifications associated with a smart device 12 identificationat entry and at exit do not match. Suitable schemes for identifying avehicle include visual detection of the vehicle by computerized imageanalysis of video data, visual detection of a licence plate number bycomputerized image analysis of video data, a magnetic signaturedetermined by a magnetometer of the parking lot when the vehicle passesby the magnetometer, receipt by the system 10 of a communications from asmart vehicle in which the communication contains a vehicleidentification number (VIN) or other vehicle identification code, othertechniques, and any combination thereof for example. The various schemesof the present invention for identifying a vehicle advantageously do notrequire any special modification of the vehicle itself nor the use ofany in-vehicle display. Communications between a smart vehicle and thesystem 10 may employ any suitable communications technology, includingcommunications technologies described herein above in respect of smartdevices 12 not integrated with a vehicle; vehicle-specificcommunications technologies such as DSRC (Dedicated Short-RangeCommunications); other communications technologies; and any combinationthereof for example.

In variations of embodiments, the open-barrier command may be issued assoon as payment processing is initiated, after payment processing issuccessfully completed, after a sufficient amount of time for paymentprocessing to occur has elapsed, or any combination thereof. Forexample, payment processing associated with some smart device 12identifications may need to be successfully completed before opening theexit barrier, while the exit barrier will be opened as soon as paymentprocessing is initiated for the same or different set or type of smartdevice 12 identifications. In some embodiments, the status associatedwith the smart device 12 identification is updated after paymentprocessing is initiated and/or completed, and in such embodiments theserver 18 determines whether to issue the open-barrier command on thebasis of the updated status.

Upon receiving the open-barrier command, the exit controller 26 opensthe exit barrier to permit the vehicle to exit the parking lot. When thevehicle has moved forward from the interior side of the exit barrier tothe exterior side of the exit barrier, the vehicle sensor 32 then sensesthe absence of a vehicle (in the exemplary scenario where anothervehicle does not immediately fill the vacant position at the exitbarrier). Also, the vehicle sensor 34 senses the presence of a vehiclewhen it arrives at the exterior side of the exit lane adjacent the exitbarrier, and the exit controller 26 closes the exit barrier.

In the first embodiment, the server 18 is operable to override theordinary operation of the exit controller 26 and issue a command for theexit controller 26 to close the exit barrier. In some embodiments, theexit controller 26 does not cause the exit barrier to close untilreceiving a close-barrier command from the server 18. In someembodiments, indications of absence and/or presence sensed by thevehicle sensor 34 are transmitted to the server 18, which transmits acommand to the exit controller 26 to close the exit barrier.

For a stall barrier that remains open during the parking session, thesystem 10 is operable to close the stall barrier (e.g. move it back intoits obstruction position or otherwise indicate access is restricted) atany time after the vehicle has vacated the parking stall. In suchembodiments, the server 18 may receive a communication from the smartdevice 12 user prior to or after vacating the parking stall, in whichcase the system 10 is preferably operable to close the stall barrierwhen the system 10 determines that no vehicle is present at the stall.For example, the system 10 may be operable to determine whether thesmart device 12 is located in or away from the restricted parking stall.Additionally or alternatively, a vehicle sensor may be located at ornear the restricted parking stall and operable to sense the absence orpresence of a vehicle at the restricted parking stall. Other techniques,such as image analysis of video data showing the restricted parkingstall may be employed, for example. In some embodiments, however, thesystem 10 is operable to close the stall barrier associated with thesmart device 12 identification when interacting with the smart device 12at an interior or outer perimeter exit barrier. Closing the stallbarrier in such embodiments is in addition to opening and closing anexit barrier for a restricted section or the outer perimeter of theparking lot.

In the exemplary scenario where the exit barrier is an outer perimeterbarrier, when the server 18 becomes aware that the exit barrier has beenopened and then closed, such as by receiving an exit-barrier status fromthe exit controller 26 as shown in FIG. 3, the server 18 is operable tostore an updated count of the number of vehicles that have exited theparking lot through the exit barrier. Additionally or alternatively, theserver 18 may store an updated count of the number of vehicles occupyingthe parking lot by incrementing the lot occupancy count each time theouter perimeter entry barrier is opened then closed and decrementing thelot occupancy count each time the outer perimeter exit barrier is openedthen closed. In variations, the server 18 may store a lot occupancypercentage, number of available parking stalls remaining, or otherrelated quantities. Typically, the lot occupancy or related quantity isstored in the database 20. In the first embodiment, the server 18 isoperable to communicate a measure of lot occupancy to other computerizedsystems (shown in FIG. 1 as additional resources 22), includingthird-party systems which may include one or more third-party parkingreservation systems for example.

In the exemplary scenario of FIG. 3, the payment processing completessuccessfully and the server 18 stores an updated value of the statusassociated with the smart device 12 identification in the database 20.

While payment processing was described as being initiated shortly beforethe exit barrier was opened according to the exemplary scenario of FIG.3, in general payment processing may occur at any suitable time. Forexample, payment processing for parking subscribers may occur atperiodic intervals independent of when parking is occurring, such as onthe first day of each month, each week or other period, etc. In someembodiments, such as where the parking fee is not time-based, paymentprocessing can occur when a vehicle is entering the parking lot,including before the entry barrier is opened to permit entry of thevehicle. In some embodiments, the payment processing occurs betweenentry and exit of the vehicle for example. While the status associatedwith a given smart device 12 identification is typically updated andstored after each payment process, the associated status may be updatedand/or stored at any time.

As shown in FIG. 3, the server 18 is operable to interact withthird-party systems (shown in FIG. 1 as additional resources 22), suchas by notifying selected third parties, if any, of the exit associatedwith the smart device 12 identification. Such exit notifications mayproceed in an analogous fashion to the entry notifications describedherein above.

In embodiments in which the server 18 in conjunction with the one ormore vehicle sensors associated with a given parking stall implement astall barrier and its associated entry and/or exit controller(s) 24 and26, the system 10 is operable to open the stall barrier by the server 18authorizing parking (e.g. prevent parking enforcement action against avehicle or its driver, such as preventing the communication of an alertinstructing that the vehicle should be towed or otherwise not issuing analert indicating non-authorization) in the given stall in response tothe sensed presence of a vehicle in the given stall, the determinedsmart device 12 location (e.g. at the given stall), and the smart device12 status (e.g. the smart device 12 user not being banned from parkingin the given stall due to prior parking infractions, the smart device 12being properly pre-registered with the system 10, other status criteria,and any combination thereof for example). Also, in such embodiments thesystem 10 is operable to close the stall barrier by authorizing exitfrom the given stall (e.g. prevent further enforcement action such aspayment collections against a smart device 12 user account, or otherwisenot issue an alert indicating non-authorization) in response to thesensed departure of the vehicle from the given stall, the determinedsmart device 12 location at the time of vehicle departure (e.g. at thegiven stall), and the smart device 12 status (e.g. the accountassociated with the smart device 12 being in compliance with paymentrequirements of the parking lot). Typically, the entry and exitauthorizations involve storing entry and exit authorization values inthe database of the system 10, respectively, such as in association withthe smart device 12 status. The server 18 may also communicatemessage(s) to the smart device 12 confirming the entry and/or exitauthorization, as each occurs for example. In some embodiments andparking lots, the stall barrier(s) associated with each given stall thatare implemented by the server 18 operation in conjunction with the oneor more vehicle sensors associated with each given stall are the onlyentry and exit barriers of the parking lot.

Thus, there is provided a computerized system for managing a parkinglot, the system including: (a) an entry beacon operable to transmit anentry-beacon identification of the entry beacon; (b) an exit beaconoperable to transmit an exit-beacon identification of the exit beacon,the exit beacon being selected from the group consisting of the entrybeacon and another beacon separate from the entry beacon; (c) a firstvehicle sensor operable to sense the presence of a first vehicle at avehicle entry location of the parking lot; (d) a second vehicle sensoroperable to sense the presence of a second vehicle at a vehicle exitlocation of the parking lot, the second vehicle sensor being selectedfrom the group consisting of the first vehicle sensor and anothervehicle sensor separate from the first vehicle sensor, the exit locationbeing selected from the group consisting of the entry location andanother location separate from the entry location, the second vehiclebeing the first vehicle or another vehicle separate from the firstvehicle; and (e) a computer-implemented server operable to receive froma smart device each of the entry-beacon identification and theexit-beacon identification, operable to determine the location of thesmart device in response to said each of the entry-beacon identificationand the exit-beacon identification, operable to determine a statusassociated with the smart device, operable to authorize an entry of thefirst vehicle when the status indicates no entry rejection of the smartdevice, the determined location of the smart device is at the entrylocation, and the first vehicle sensor senses the presence of the firstvehicle at the entry location, operable to determine an updated value ofthe status in response to a payment transaction associated with thesmart device, and operable to authorize an exit of a second vehicle whenthe status indicates no exit rejection of the smart device, thedetermined location of the smart device is at the exit location, and thesecond vehicle sensor senses that the second vehicle is at the exitlocation.

Method of Operation

Referring to FIGS. 1 and 4, the read/write memory of the server 18 inaccordance with the first embodiment of the invention contains blocks ofcode comprising computer executable instructions for directing the CPUor other processing circuit of the server 18 to perform operations ofthe parking controller system 10. Also, in the first embodiment theentry controller 24 memory, exit controller 26 memory, an entry beacon35 memory and an exit beacon 36 memory each contain blocks of codecomprising computer executable instructions for directing the entrancegate controller 24 CPU, exit gate controller 26 CPU, entry beacon 35CPU, and exit beacon 36 CPU, respectively. Collectively, the CPUs of theparking controller system 10 are directed to perform respective steps ofa method shown generally at 38.

Additionally or alternatively, one or more of such blocks of code mayform part of a computer program product comprising computer executableinstructions embodied in a non-transitory computer readable medium.

When electrical power is being supplied to the various CPUs of theparking controller system 10, the server 18 CPU is directed to beginexecuting the instructions of block 40.

Block 40 directs the server 18 CPU to receive an entry requestidentifying a smart device 12. Receiving an entry request identifying asmart device 12 typically involves receiving or otherwise determining atelephone number identifying the smart device 12. However, any suitableunique identifier may be employed. The server 18 may receivecommunications directly from the smart device 12 via the direct link 14and/or via the Internet 16 for example.

After block 40 has been executed, block 42 then directs the server 18CPU to determine the location of the particular smart device 12 fromwhich the entry request had been received. Typically, the entry requestincludes the identification code of a beacon 35 or 36. However, in someembodiments communications other than the entry request per se areemployed for the server 18 to receive the beacon 35 or 36identification. Such other communications may occur prior to or afterthe entry request is transmitted. In the first embodiment, determiningthe location of the smart device 12 involves querying the database 20 orotherwise searching memory for an association between the receivedbeacon 35 or 36 identification and an entry or exit barrier, such as byidentifying an entry or exit controller 24 or 26 that corresponds to thereceived beacon 35 or 36 identification. In some embodiments, the smartdevice 12 also communicates to the server 12 a distance between thesmart device 12 and each identified beacon 35 and/or 36, such that theserver 18 is able to determine the location of the smart device 12 withgreater accuracy.

In a variation of embodiments, block 42 may direct a location sensor CPUto determine the location of the particular smart device 12 from whichthe entry request had been received, such as by a plurality of wirelesscommunications devices (not shown) receiving the communicationtransmitted wirelessly from the smart device 12 and determining thelocation by trilateration of the multiply-received communication.

After executing block 42, block 44 directs the server 18 CPU todetermine whether the location is an entry location. Determining whetherthe location is an entry location typically involves determining whetherthe location determined by block 42 is associated with an entry lane onthe exterior side of an entry barrier, such as by being associated witha given entry barrier and/or the entry controller 24 (FIG. 1). Invariations, the boundary of the entry location will vary but typicallyis commensurate with being bounded by the entry lane no more than onevehicle's distance away from the entry barrier on the exterior sidethereof. In some embodiments, determining whether the location is anentry location involves determining the location of the smart device 12multiple times as it moves within the vicinity of the entry beacon 35until the location of the smart device 12 is determined by the server 18to be at the entry location. Determining whether the location is anentry location may involve determining that the location(s) of the smartdevice 12 has been within the bounds of the entry location for a minimumperiod of time, which may be in the range of a few microseconds toseveral seconds for example. If by executing block 44 the location isdetermined not to be an entry location, block 46 directs the server 18CPU to perform error handling operations, which in variations mayinclude waiting for the smart device 12 to move into the entry location,waiting until a time-out occurs, executing an error handling routinefollowing a time-out, transmitting an error message to the smart device12, updating the status associated with the smart device 12identification, ignoring the previously received entry request, othererror handling procedures, and any combination thereof for example.

In some embodiments, a location sensor (as an enhanced variation of thebeacons 35 and 36) determines whether the smart device 12 location is anentry location, and may communicate a final determination to the server18 for example. Additionally or alternatively, some or all of the errorhandling operations of block 46 may be executed by the location sensorCPU (not shown).

After block 46 has been executed, the process returns to block 42.

If by block 44 the location is determined to be an entry location, thenblock 48 directs the server 18 CPU to determine whether a vehicle ispresent in the vehicle entry location (e.g. in the lane on the exteriorside of the entry barrier). In the first embodiment, determining whethera vehicle is present involves sensing the presence of a vehicle by thevehicle sensor 28, detecting the sensed presence by the entry controller24, and transmitting by the entry controller 24 to the server 18 anindication of the presence. In some embodiments, determining whether avehicle is present involves multiple communications to the server 18 ofan indication of the presence or absence of a vehicle until anindication of presence is received by the server 18. In someembodiments, determining whether a vehicle is present involves multipledeterminations of the presence or absence of a vehicle followed by onecommunication by the entry controller 24 to the server 18 when thepresence is determined. In some embodiments, determining whether avehicle is present involves detecting or receiving by the server 18 thesensed presence directly from the vehicle sensor 28. In someembodiments, block 48 directs the entry controller 24 CPU to determinewhether a vehicle is present.

If by block 48 it is determined that no vehicle is present, then block50 directs the server 18 CPU to perform error handling operations, whichin variations may include waiting for a vehicle to become present in thevehicle entry location, waiting until a time-out occurs, executing anerror handling routine following a time-out, transmitting an errormessage to the smart device 12, updating the status associated with thesmart device 12 identification, other error handling procedures, and anycombination thereof for example. In some embodiments, some or all of theerror handling operations of block 50 are executed by the entrycontroller 24 CPU.

After block 50 has been executed, the process in the first embodimentreturns to block 42. However, in some embodiments (not shown), theprocess returns to block 48.

If by block 48 it is determined that a vehicle is present, then block 52directs the server 18 CPU to determine a status associated with thesmart device 12. Determining a status associated with the smart device12 involves in the first embodiment querying the database 20 for thestatus associated with the smart device 12 identification that waspreviously obtained by the server 18 when block 40 was executed.

Block 54 directs the server 18 CPU to determine whether the statusassociated with the smart device 12 identification indicates an entryrejection. The status may indicate an entry rejection in a variety ofcircumstances suited to particular embodiments of the invention, such asif it is determined by block 52 that no status exists for the smartdevice 12 identification because the given smart device 12 is notpre-registered with the server 18, if the status indicates that thesmart device 12 is not in compliance with payment requirements of theserver 18, if the status indicates that the smart device 12 isassociated with a person who has been banned from the parking lot formisconduct or other reasons, if the status indicates that the smartdevice 12 identification has been flagged as a fraudulent, incorrect,non-existent, or otherwise improper telephone number or other smartdevice 12 identification, or any combination thereof for example. Otherstatus conditions are possible. Different parking lots may havedifferent rules for determining whether a given status indicates anentry rejection, for example.

If by block 54 the server 18 CPU determines that the status indicates anentry rejection, then block 56 directs the server 18 CPU to performerror handling operations, which in variations may include transmittingan error message to the smart device 12 for display on the smart device12 display screen, opening an informational webpage in a browser of thesmart device 12, issuing an alert for a human attendant to assist thesmart device 12 user, initiation of a telephone call between the smartdevice 12 and a telephone associated with the parking lot (e.g. callcenter), transmitting an audio message to the smart device 12, updatingthe status associated with the smart device 12 identification, othererror handling procedures, and any combination thereof for example.

After block 56 has been executed, the process in the first embodimentreturns to block 40. However, in various embodiments (not shown), theprocess returns to any one of blocks 42, 44, 48 and 54, for example. Insome embodiments, the particular error handling steps taken by block 56determine the block to which the process returns after block 56 has beenexecuted.

If by block 54 the server 18 CPU determines that the status indicatesthere is no entry rejection of the smart device 12, then block 58directs the entry controller 24 CPU to cause the entry barrier to open.In the first embodiment, opening the entry barrier involves transmittingan open-barrier command by the server 18 CPU to the entry controller 24.In the case of an entry gate or blockade, the entry controller 24typically controls a motor that causes the entry gate or blockade toopen (e.g. rotate, slide or otherwise move into an non-obstructingposition). For a spanning catenary, the length of the cable or similarcan be increased or decreased so that the catenary is lowered to belevel with the ground or raised above the height of the vehicle,respectively, for example. Where the entry barrier is a visualindicator, however, the entry controller 24 is operable to alter thedisplay of the visual indicator (e.g. change a red light to a greenlight) so as to open the entry barrier. Where the entry barrier is anaudible indicator, the sound (e.g. automated verbal command) of theaudible indicator can be selected to indicate a vehicle is permitted topass, so as to open the entry barrier. Combinations of such entrybarriers may be employed, for example.

In embodiments in which the server 18 in conjunction with the one ormore vehicle sensors associated with a given parking stall implement astall barrier and its associated entry and/or exit controller(s) 24 and26, block 58 typically directs the server 18 CPU to open the entrybarrier by communicating a message to the smart device 12 indicatingentry authorization (e.g. “Welcome, payment will be processed accordingto your payment preferences.”). Additionally or alternatively, block 58may direct the server 18 CPU to store in the database 20 (FIG. 1) anentry authorization value such that the server 18 does not issue analert to commence parking enforcement action against the vehicle presentin the given stall. In such embodiments in which the server 18 and theone or more vehicle sensors associated with a given parking stallimplement a stall barrier, the functionality of block 58 may beconsidered to have been performed by block 54 upon determination by theserver 18 CPU that the status indicates there is no entry rejection ofthe smart device 12. While FIG. 4 shows a particular sequence forexecuting blocks 44, 48 and 54, in general these blocks may be executedin any order.

Block 60 directs the entry controller 24 CPU to determine whether avehicle has entered past the entry barrier, such as an entrance gate(not shown). Determining whether a vehicle has entered past the entrybarrier involves determining whether the vehicle at the entry locationhas vacated the entry location and become present at the interior sideof the entry barrier. In the first embodiment, such method step involvessensing by the vehicle sensor 28 the absence of a vehicle andsubsequently sensing by the vehicle sensor 30 the presence of a vehicle;and detecting the sensed absence and the sensed presence by the entrycontroller 24. In some embodiments, executing block 60 also involvescommunicating indications of vehicle absence and/or presence by theentry controller 24 to the server 18. In some embodiments, determiningwhether the vehicle has entered involves multiple sensing by the vehiclesensors 28 and 30 until a vehicular entry is determined. In someembodiments, determining whether the vehicle has entered involvesreceiving by the server 18 sensed absence and/or presence directly fromthe vehicle sensor 28 and/or from the vehicle sensor 30. In someembodiments, block 60 directs the server 18 CPU to determine whether thevehicle has entered.

If by block 60 it is determined that a vehicle has not entered, thenblock 62 directs the server 18 CPU to perform error handling operations,which in the first embodiment involves communicating by the entrycontroller 24 to the server 18 an indication that the vehicle has notentered, such as not entering after a specifiable time-out period haselapsed. In variations, performing error handling operations may includetransmitting an error message to the smart device 12 for display on thesmart device 12 display screen, opening an informational webpage in abrowser of the smart device 12, issuing an alert for a human attendantto assist the smart device 12 user, initiation of a telephone callbetween the smart device 12 and a telephone associated with the parkinglot, transmitting an audio and/or text message to the smart device 12,updating the status associated with the smart device 12 identification,displaying video of the scene captured by a security camera, issuing analert to a human attendant to view video display of the scene, othererror handling procedures, and any combination thereof for example.

After block 62 has been executed, the process in the first embodimentreturns to block 40. However, in various embodiments (not shown), theprocess returns to any one of blocks 42, 44, 48, 54 and 60, for example.In some embodiments, the particular error handling steps taken by block62 determine the block to which the process returns after block 62 hasbeen executed.

If by block 60 it is determined that the vehicle has entered, then block64 directs the entry controller 24 CPU to cause the entry barrier toclose. In some embodiments, such as where it is the server 18 thatdetermines whether the vehicle has entered, closing the entry barrierinvolves transmitting a close-barrier command by the server 18 CPU tothe entry controller 24. In some embodiments, block 64 directs theserver 18 CPU to directly cause the entry barrier to close. Inembodiments in which the server 18 in conjunction with the one or morevehicle sensors associated with a given parking stall implement a stallbarrier and its associated entry and/or exit controller(s) 24 and 26,block 64 is typically omitted.

After executing block 64 such that the entry barrier is closed, block 66directs the server 18 CPU to store an entry timestamp, increment thevehicle count, and notify selected third parties, if any, of the entryassociated with the smart device 12 identification. In the firstembodiment, executing block 66 involves transmitting by the entrycontroller 24 to the server 18 an entry status indicating that the entrybarrier is closed. In some embodiments, executing block 66 involvestransmitting the entry status in association with the smart device 12identification. In the first embodiment, storing a timestamp involvesstoring the current time in the database 20 in association with thesmart device 12 identification, and incrementing the vehicle countinvolves updating a vehicle count stored in the database 20. In thefirst embodiment, notifying selected third parties involvescommunicating notifications, if any, indicating a parking session hasbegun. The notifications are typically communicated in response to alist of third-party systems (shown in FIG. 1 as additional resources22), such as parking reservation systems or third-party systems thatwere previously selected by the smart device 12 user to be notified whenthe smart device 12 user arrives at the parking lot.

Still referring to FIG. 4, in embodiments having further entry barriersvarious steps of the method 38 shown in FIG. 4 may be repeated at eachof the further entry barriers. For example, blocks 42 to 66 may berepeatedly executed. In some embodiments where repeated confirmations ofthe smart device 12 identification are desirable, blocks 40 to 66 may berepeatedly executed. For barriers such as stall barriers that remainopen during the parking session, block 64, or blocks 60 to 64, may beomitted and the method 38 proceed from block 58 or 60 directly to block66, for example.

Referring to FIGS. 4 and 5, after block 66 has been executed, at theconclusion of the parking session, block 68 in the first embodimentdirects the server 18 CPU to receive an exit request identifying a smartdevice 12. In the first embodiment, receiving the entry request alsoinvolves communicating the smart device 12 identification by the smartdevice 12 to the server 18, such as by the direct link 14 (FIG. 1)and/or by the Internet 16 (FIG. 1). Receiving an entry requestidentifying a smart device 12 typically involves receiving or otherwisedetermining a telephone number identifying the smart device 12. However,any suitable unique identifier may be employed. In some embodiments,block 68 directs the server 18 CPU to receive an exit requestidentifying a smart device 12, such as by the server 18 receivingcommunications from a location sensor (not shown) after the locationsensor has received the smart device 12 identification directly from thesmart device 12 for example.

After block 68 has been executed, block 70 then directs the server 18CPU to determine the location of the particular smart device 12 fromwhich the entry request had been received. Typically, the entry requestincludes the identification code of a beacon 35 or 36. However, in someembodiments communications other than the entry request per se areemployed for the server 18 to receive the beacon 35 or 36identification. Such other communications may occur prior to or afterthe entry request is transmitted. In the first embodiment, determiningthe location of the smart device 12 involves querying the database 20 orotherwise searching memory for an association between the receivedbeacon 35 or 36 identification and an entry or exit barrier. In someembodiments, the smart device 12 also communicates to the server 12 adistance between the smart device 12 and each identified beacon 35and/or 36, such that the server 18 is able to determine the location ofthe smart device 12 with greater accuracy.

In a variation, block 70 may direct a location sensor CPU (not shown) todetermine the location of the particular smart device 12 from which theexit request had been received. In such variation, determining thelocation of the smart device 12 involves receiving the communicationtransmitted from the smart device 12 by a plurality of wirelesscommunications devices (not shown), such as near-field wirelesscommunications devices (not shown), and determining the location bytrilateration of the multiply-received communication.

After executing block 70, block 72 directs the server 18 CPU todetermine whether the location is an exit location. Determining whetherthe location is an exit location typically involves determining whetherthe location determined by block 42 is associated with an entry lane onthe exterior side of an entry barrier, such as by being associated witha given entry barrier and/or the entry controller 24 (FIG. 1). Invariations, the boundary of the exit location will vary but typically iscommensurate with being bounded by the exit lane no more than onevehicle's distance away from the exit barrier on the interior sidethereof. In some embodiments, determining whether the location is anexit location involves determining the location of the smart device 12multiple times as it moves within the vicinity of the exit beacon 36until the location of the smart device 12 is determined by the server 18to be at the exit location. Determining whether the location is an exitlocation may involve determining that the location(s) of the smartdevice 12 has been within the bounds of the exit location for a minimumperiod of time, which may be in the range of a few microseconds toseveral seconds for example.

If by executing block 72 the location is determined not to be an exitlocation, block 74 directs the server 18 CPU to perform error handlingoperations, which in variations may include performing operationssimilar to those described herein above in respect of block 46 (FIG. 4),with references in such description to entry or entrance being replacedby exit.

In some embodiments, a location sensor (as an enhanced variation of thebeacon 35 and/or 36) determines whether the smart device 12 location isan exit location, and may communicate a final determination to theserver 18 for example. Additionally or alternatively, some or all of theerror handling operations of block 74 may be executed by the locationsensor CPU (not shown).

After block 74 has been executed, the process returns to block 70.

If by block 72 the location is determined to be an exit location, thenblock 76 directs the server 18 CPU to determine whether a vehicle ispresent at the vehicle exit location associated with the smart device 12exit location determined by block 72. In the first embodiment,determining whether a vehicle is present involves sensing the presenceof a vehicle by the vehicle sensor 32, detecting the sensed presence bythe exit controller 26, and transmitting by the exit controller 26 tothe server 18 an indication of the presence. In some embodiments,determining whether a vehicle is present involves multiplecommunications to the server 18 of an indication of the presence orabsence of a vehicle until an indication of presence is received by theserver 18. In some embodiments, determining whether a vehicle is presentinvolves multiple determinations of the presence or absence of a vehiclefollowed by one communication by the exit controller 26 to the server 18when the presence is determined. In some embodiments, determiningwhether a vehicle is present involves detecting or receiving by theserver 18 the sensed presence directly from the vehicle sensor 32. Insome embodiments, block 76 directs the exit controller 26 CPU todetermine whether a vehicle is present.

If by block 76 it is determined that no vehicle is present, then block78 directs the server 18 CPU to perform error handling operations, whichin variations may include performing operations similar to thosedescribed herein above in respect of block 50 (FIG. 4), with referencesin such description to entry or entrance being replaced by exit. In someembodiments, some or all of the error handling operations of block 78are executed by the exit controller 26 CPU.

After block 78 has been executed, the process in the first embodimentreturns to block 70. However, in some embodiments (not shown), theprocess returns to block 72.

If by block 76 it is determined that a vehicle is present, then block 80directs the server 18 CPU to retrieve the status associated with thesmart device 12 identification and to collect a parking fee. In thefirst embodiment, retrieving the status involves querying the database20 for the status associated with the smart device 12 identification.

Referring to FIG. 6, an exemplary method for directing the server 18 CPUto perform steps of block 80 related to collecting a parking fee isshown generally at 82.

Method 82 begins execution at block 84, which directs the server 18 CPUin the first embodiment to determine whether the status associated withthe smart device 12 identification indicates a non-fee rejection (i.e.an exit rejection for a reason other than payment of the parking fee, ifany, for the current parking session).

If by block 84 the server 18 determines that the status does indicate anon-fee rejection, then the process is directed to return to the method38 at block 80. In some embodiments, the process is directed to returnto the method 38 at block 102 described herein below.

If by block 84 the server 18 determines that the status does notindicate a non-fee rejection, then block 86 directs the server 18 CPU todetermine whether the status associated with the smart device 12identification indicates that the financial account associated with thesmart device 12 identification is fully paid (i.e. zero dollars owed). Adetermination that the smart device 12 account is fully paid may occurin the case of subscribers of time-unlimited parking during the periodbetween periodic (e.g. monthly) payments, in the case when a parking feewas collected prior to exiting such as at entry, other situations, orany combination thereof for example.

If by block 86 the server 18 determines that the status indicates afully paid account, then the process is directed to execute block 98described herein below.

If by block 86 the server 18 determines that the status does notindicate a fully paid account, including possibly owing for the currentparking session, then block 88 directs the server 18 CPU to calculate aparking fee. In various embodiments, calculating a parking fee involvesany suitable calculation method, pricing scheme, or the like. Forexample, the parking fee may be calculated by multiplying a knownparking rate by the duration of the current parking session, thenpossibly adding any amounts in arrears plus penalties or surcharges, ifany, for example. In some embodiments, calculating a parking feeinvolves selecting an applicable parking rate from a plurality ofparking rates associated with the parking lot. In some embodiments,calculating a parking fee involves selecting an applicable parking rateassociated with the smart device 12 identification. In some embodiments,calculating a parking fee involves selecting an applicable parking rateassociated with the smart device 12 status. In some embodiments,calculating a parking fee includes deducting an amount from the nominalfee, such as where a local business has offered to pay for a portion orall of the parking costs for parking to visit that business for example.In some embodiments, the server 18 receives the parking rate in acommunication from an additional resource 22 (FIG. 1), such as acomputerized third-party system for example.

After block 88 has been executed, block 90 then directs the server 18CPU to prompt the smart device 12 for fee acceptance. In the firstembodiment, prompting the smart device 12 for fee acceptance involvestransmitting the fee by the server 18 to the smart device 12. Thecommunications between the server 18 and the smart device 12 may beimplemented by any suitable communications technology (e.g. near-fieldwireless communications, direct link 14, Internet 16, cellular telephonecommunications, satellite communications, other communications links,and any combination thereof for example). The smart device 12 CPU isthen directed by its installed application program to display a feeprompt on a display screen of the smart device 12.

In some embodiments having a location sensor (implemented as an enhancedvariation of the beacon 35 and/or 36) operable to conduct two-waycommunications with the smart device 12, block 90 may direct thelocation sensor to prompt the smart device 12 for fee acceptance, suchas after the server 18 has transmitted the fee amount to the locationsensor.

After block 90 has been executed, block 92 then directs the server 18CPU to determine whether the parking fee has been accepted by the smartdevice 12. In the first embodiment, determining whether the parking feehas been accepted involves waiting to receive confirmation of acceptanceor rejection from the smart device 12. Such confirmation may betransmitted by the smart device 12 in response to user input following aprompt displayed on the smart device 12, for example. In someembodiments, however, no user input is required and block 92 is omittedsuch that the method 82 proceeds directly after block 88 to block 96described herein below. In the first embodiment, confirmation ofrejection of the parking fee is determined by receiving a communicationfrom the smart device 12 indicating the parking fee is not accepted.Additionally or alternatively, in some embodiments confirmation ofrejection is determined by a time-out condition in which there is afailure to receive confirmation of acceptance after waiting aspecifiable time-out duration.

If by block 92 the server 18 determines that the parking fee is notaccepted by the smart device 12, then block 94 directs the server 18 CPUto perform error handling operations, which in variations may includeupdating a monetary account associated with the smart device 12identification, transmitting an error message to the smart device 12 fordisplay on the smart device 12 display screen, opening an informationalwebpage in a browser of the smart device 12, issuing an alert for ahuman attendant to assist the smart device 12 user, initiation of atelephone call between the smart device 12 and a telephone associatedwith the parking lot, transmitting an audio and/or text message to thesmart device 12, displaying video of the scene captured by a securitycamera to a human attendant, issuing an alert to a human attendant toview the video display of the scene, flagging the smart device 12account for subsequent invoicing, other error handling procedures, andany combination thereof for example.

If by block 92 the server 18 determines that the parking fee has beenaccepted by the smart device 12, then block 96 directs the server 18 CPUto initiate a payment transaction. Initiating a payment transaction mayinvolve invoking any suitable payment transaction technology (e.g.credit card transaction, digital wallet, online money transfer service,etc.), including requesting payment processing by a third-party paymentprocessing service (e.g. third-party credit card transaction,third-party digital wallet, third-party online money transfer service,etc.) accessible as an additional resource 22 for example. In someembodiments, block 96 directs the server 18 CPU to wait until completionof payment processing is confirmed before ending block 96, while in thefirst embodiment the server 18 CPU is directed to end execution of block96 immediately after initiating the payment transaction.

After block 94 or 96 has been executed, block 98 then directs the server18 CPU to update the status of the smart device 12. Typically, updatingthe status of the smart device 12 involves updating the database 20contents to reflect the current payment status associated with the smartdevice 12 identification. In some embodiments, executing block 98involves waiting until receiving confirmation of successful paymentprocessing, if any. In some embodiments, however, updating the statusinvolves updating the database 20 contents to reflect the initiation ofpayment processing, if any, such that a separate updating of the statuscan occur upon completion of payment processing.

After block 98 has been executed, the process is directed to end themethod 82 and return to block 80 of the method 38 (FIG. 5).

Referring back to FIG. 5, after block 80 has been executed, block 100then directs the server 18 CPU to determine whether the statusassociated with the smart device 12 identification indicates an exitrejection. The status may indicate an exit rejection in a variety ofcircumstances suited to particular embodiments of the invention, such asif the status indicates that the smart device 12 is not in compliancewith payment requirements of the server 18, if an attempted paymenttransaction failed to successfully complete, or other status conditionsfor example.

If by block 100 the server 18 CPU determines that the status indicatesan exit rejection, then block 102 directs the server 18 CPU to performerror handling operations, which in variations may include performingoperations similar to those described herein above in respect of block56 (FIG. 4).

After block 102 has been executed, the process in the first embodimentreturns to block 68. However, in various embodiments (not shown), theprocess returns to any one of blocks 70, 72, 76 and 100, for example. Insome embodiments, the particular error handling steps taken by block 102determine the block to which the process returns after block 102 hasbeen executed.

If by block 100 the server 18 CPU determines that the status indicatesthere is no exit rejection of the smart device 12, then block 104directs the exit controller 26 CPU to cause the exit barrier to open. Inthe first embodiment, opening the exit barrier involves transmitting anopen-barrier command by the server 18 CPU to the exit controller 26. Inembodiments in which the server 18 in conjunction with the one or morevehicle sensors associated with a given parking stall implement a stallbarrier and its associated entry and/or exit controller(s) 24 and 26,block 104 typically directs the server 18 CPU to open the exit barrierby communicating a message to the smart device 12 indicating exitauthorization (e.g. “Thank you for parking with us. Parking charges arecollected in accordance with your payment preferences.”). Additionallyor alternatively, block 104 may direct the server 18 CPU to store in thedatabase 20 (FIG. 1) an exit authorization value so as to preventenforcement action such as further payment collections processingagainst the smart device 12 user account. In such embodiments in whichthe server 18 and the one or more vehicle sensors associated with agiven parking stall implement a stall barrier, the functionality ofblock 104 may be considered to have been performed by block 100 upondetermination by the server 18 CPU that the status indicates there is noexit rejection of the smart device 12. While FIG. 5 shows a particularsequence for executing blocks 72, 76 and 100, in general these blocksmay be executed in any order.

Block 106 directs the exit controller 26 CPU to determine whether avehicle has exited past the exit barrier, such as an exit gate (notshown). Determining whether a vehicle has exited past the exit barrierinvolves determining whether the vehicle at the exit location hasvacated the exit location and become present at the exterior side of theexit barrier. In the first embodiment, such method step involves sensingby the vehicle sensor 32 the absence of a vehicle and subsequentlysensing by the vehicle sensor 34 the presence of a vehicle; anddetecting the sensed absence and the sensed presence by the exitcontroller 26. In some embodiments, executing block 106 also involvescommunicating indications of vehicle absence and/or presence by the exitcontroller 26 to the server 18. In some embodiments, determining whetherthe vehicle has exited involves multiple sensing by the vehicle sensors32 and 34 until a vehicular exit is determined. In some embodiments,determining whether the vehicle has exited involves receiving by theserver 18 sensed absence and/or presence directly from the vehiclesensor 32 and/or from the vehicle sensor 34. In some embodiments, block106 directs the server 18 CPU to determine whether the vehicle hasexited.

If by block 106 it is determined that a vehicle has not exited, thenblock 108 directs the server 18 CPU to perform error handlingoperations, which in the first embodiment involves communicating by theexit controller 26 to the server 18 an indication that the vehicle hasnot exited. In variations, performing error handling operations mayinclude performing operations similar to those described herein above inrespect of block 62 (FIG. 4).

After block 108 has been executed, the process in the first embodimentreturns to block 68. However, in various embodiments (not shown), theprocess returns to any one of blocks 70, 72, 76, 100 and 106, forexample. In some embodiments, the particular error handling steps takenby block 108 determine the block to which the process returns afterblock 108 has been executed.

If by block 106 it is determined that the vehicle has exited, then block110 directs the exit controller 26 CPU to cause the exit barrier toclose. In some embodiments, such as where it is the server 18 thatdetermines whether the vehicle has exited, closing the exit barrierinvolves transmitting a close-barrier command by the server 18 CPU tothe exit controller 26. In some embodiments, block 110 directs theserver 18 CPU to directly close the exit barrier. In embodiments inwhich the server 18 in conjunction with the one or more vehicle sensorsassociated with a given parking stall implement a stall barrier and itsassociated entry and/or exit controller(s) 24 and 26, block 110 istypically omitted.

For a barrier such as a stall barrier that remains open during theparking session, the method 38 involves closing the stall barrier (e.g.moving it back into its obstruction position or otherwise indicatingthat access is restricted) at any time after the vehicle has vacated theparking stall. In some embodiments, the method involves closing thestall barrier as soon as it is determined that the vehicle has vacatedthe restricted parking stall, while in some embodiments the methodinvolves closing the stall barrier when the outer perimeter exit barrieris being closed, or at any time therebetween. For example, the method 38may involve closing the stall barrier after executing block 100 if thestatus associated with the smart device 12 identification indicatesthere is no exit rejection of the smart device 12, a vehicle wasdetermined by block 76 to be present at an outer perimeter or interiorexit location away from the restricted parking stall, and the smartdevice 12 location was determined by block 72 to be at an outerperimeter or interior exit location away from the restricted parkingstall. The method may involve closing a stall barrier in addition toopening and/or closing other exit gate(s).

After block 110 has been executed, block 112 then directs the server 18CPU to store an exit timestamp, decrement the vehicle count, and notifyselected third parties of the exit associated with the smart device 12identification. In the first embodiment, executing block 112 involvestransmitting by the exit controller 26 to the server 18 an exit-barrierstatus indicating that the exit barrier is closed. In some embodiments,executing block 112 involves transmitting the exit-barrier status inassociation with the smart device 12 identification. In the firstembodiment, storing an exit timestamp involves storing the current timein the database 20 in association with the smart device 12identification, and decrementing the vehicle count involves updating avehicle count stored in the database 20. In the first embodiment,notifying selected third parties involves communicating notifications,if any, indicating a parking session has ended. The notifications aretypically communicated in response to a list of third-party systems(shown in FIG. 1 as additional resources 22), such as parkingreservation systems or third-party systems that were previously selectedby the smart device 12 user to be notified when the smart device 12 userexits from the parking lot.

In embodiments having further exit barriers, various steps of the method38 shown in FIG. 5 may be repeated at each of the further exit barriers.For example, blocks 70 to 80 and 100 to 110 may be repeatedly executed,with the exception that typically the parking fee for a given parkingsession is only collected once. In some embodiments where repeatedconfirmations of the smart device 12 identification are desirable, block68 may also be repeated. Block 112 is typically executed only once foreach parking session.

After block 112 has been executed, the server 18 CPU is directed to endthe method 38.

While FIGS. 4 to 6 show initiating a payment transaction by executingblock 96 of FIG. 6 at the conclusion of a parking session prior toexiting the parking lot, in general block 96 may be executed at any timebefore, during or after a given parking session.

While not shown in FIGS. 4 to 6, the method 38 includes in someembodiments the step(s) of providing parking lot information from theserver 18 to the smart device 12 in a manner described herein above inrespect of FIG. 2. Such provision of parking lot information may occurat any time before, during or after execution of the method 38 shown inFIGS. 4 to 6.

Thus, there is provided a computer-implemented method of managing aparking lot, the method involving: (a) authorizing an entry of a firstvehicle by a computerized parking controller in response to a statusindicating no entry rejection of a smart device, a first locationindicating that the smart device is located at an entry location of theparking lot, and a first presence indicating that the first vehicle ispresent at the entry location, the first location being determined bythe parking controller in response to an entry-beacon identification ofan entry beacon of the parking lot, the entry-beacon identificationbeing communicated to the parking controller by the smart device in afirst communication; (b) determining by the parking controller anupdated value of the status in response to a payment transactionassociated with the smart device; and (c) authorizing an exit of asecond vehicle by the parking controller in response to the statusindicating no exit rejection of the smart device, a second locationindicating that the smart device is located at an exit location of theparking lot, and a second presence indicating that the second vehicle ispresent at the exit location, the second location being determined bythe parking controller in response to an exit-beacon identification ofan exit beacon of the parking lot, the exit beacon being selected fromthe group consisting of the entry beacon and another beacon separatefrom the entry beacon, the exit-beacon identification being communicatedto the parking controller by the smart device in a second communication,the exit location being selected from the group consisting of the entrylocation and another location separate from the entry location, thesecond vehicle being the first vehicle or another vehicle separate fromthe first vehicle.

While embodiments of the invention have been described and illustrated,such embodiments should be considered illustrative of the inventiononly. The invention may include variants not described or illustratedherein in detail. Thus, the embodiments described and illustrated hereinshould not be considered to limit the invention as construed inaccordance with the accompanying claims.

What is claimed is:
 1. A computer-implemented method of managing aparking lot, the method comprising: (a) authorizing an entry of a firstvehicle by a computerized parking controller in response to a statusindicating no entry rejection of a smart device, a first locationindicating that the smart device is located at an entry location of theparking lot, and a first presence indicating that the first vehicle ispresent at the entry location, the first location being determined bythe parking controller in response to an entry-beacon identification ofan entry beacon of the parking lot, the entry-beacon identificationbeing communicated to the parking controller by the smart device in afirst communication; (b) determining by the parking controller anupdated value of the status in response to a payment transactionassociated with the smart device; and (c) authorizing an exit of asecond vehicle by the parking controller in response to the statusindicating no exit rejection of the smart device, a second locationindicating that the smart device is located at an exit location of theparking lot, and a second presence indicating that the second vehicle ispresent at the exit location, the second location being determined bythe parking controller in response to an exit-beacon identification ofan exit beacon of the parking lot, the exit beacon being selected fromthe group consisting of the entry beacon and another beacon separatefrom the entry beacon, the exit-beacon identification being communicatedto the parking controller by the smart device in a second communication,the exit location being selected from the group consisting of the entrylocation and another location separate from the entry location, thesecond vehicle being the first vehicle or another vehicle separate fromthe first vehicle.
 2. The method of claim 1 wherein step (c) comprisesdetermining by the parking controller whether the second vehicle isidentified as the first vehicle.
 3. The method of claim 1 wherein theparking lot has an entry barrier for regulating entries at the entrylocation, and wherein step (a) comprises opening the entry barrier bythe parking controller so as to authorize the entry of the firstvehicle.
 4. The method of claim 1 wherein the parking lot has an exitbarrier for regulating exits at the exit location, and wherein step (c)comprises opening the exit barrier by the parking controller so as toauthorize the exit of the second vehicle.
 5. The method of claim 3wherein the parking lot has an exit barrier for regulating exits at theexit location, the exit barrier being selected from the group consistingof the entry barrier and another barrier separate from the entrybarrier, and wherein step (c) of claim 1 comprises opening the exitbarrier by the parking controller so as to authorize the exit of thesecond vehicle.
 6. The method of claim 1 wherein step (a) comprisesreceiving by the parking controller the first communication generated bythe smart device in response to the smart device receiving no more thana single user command entered into the smart device.
 7. The method ofclaim 1 wherein step (c) comprises receiving by the parking controllerthe second communication generated by the smart device in response tothe smart device receiving no more than a single user command enteredinto the smart device.
 8. The method of claim 1 wherein step (a)comprises authorizing the entry of the first vehicle in response to anidentification of the smart device selected from the group consisting ofa telephone number, device identification code, licence plate number, animage of a licence plate, driver's licence number, an image of adriver's licence, officially-issued identification number, an image ofan officially-issued identification certificate, a vehicleidentification code, and a financial card number.
 9. The method of claim1 wherein step (c) comprises authorizing the exit of the second vehiclein response to the status indicating that the smart device is registeredwith the parking controller and is in compliance with paymentrequirements of the parking controller.
 10. The method of claim 1wherein step (a) comprises authorizing the entry of the first vehicle inresponse to the status indicating that the smart device is registeredwith the parking controller and is in compliance with paymentrequirements of the parking controller.
 11. The method of claim 9wherein step (a) of claim 1 comprises authorizing the entry of the firstvehicle in response to the status indicating that the smart device isregistered with the parking controller and is in compliance with paymentrequirements of the parking controller.
 12. The method of claim 1further comprising determining by the parking controller a parking feein response to a parking rate associated with the smart device.
 13. Themethod of claim 12 wherein determining by the parking controller aparking fee in response to a parking rate associated with the smartdevice comprises determining the parking fee in response to a durationof time spent parking.
 14. The method of claim 1 wherein step (a)comprises opening a stall barrier by the parking controller so as toauthorize the entry of the first vehicle.
 15. The method of claim 3further comprising opening a second entry barrier by the parkingcontroller in response to the status indicating no second-entryrejection and to a third location determined by the parking controller,the third location indicating that the smart device is located inproximity to an entrance side of the second entry barrier.
 16. Themethod of claim 15 wherein opening a second entry barrier by the parkingcontroller in response to the status indicating no second-entryrejection and to a third location determined by the parking controller,the third location indicating that the smart device is located inproximity to an entrance side of the second entry barrier, comprisesopening a stall barrier.
 17. The method of claim 16 further comprisingdetermining by the parking controller a parking fee in response to aparking rate associated with the smart device and a duration of timespent parking.
 18. The method of claim 1 further comprisingcommunicating by the parking controller to at least one of the smartdevice and a computerized third-party system a notification generated bythe parking controller in response to the parking controller authorizingthe entry of the first vehicle, the notification indicating the entry ofthe first vehicle in association with the smart device.
 19. The methodof claim 1 further comprising communicating by the parking controller toat least one of the smart device and a computerized third-party system anotification generated by the parking controller in response to theparking controller authorizing the exit of the second vehicle, thenotification indicating the exit of the second vehicle in associationwith the smart device.
 20. The method of claim 15 further comprisingcommunicating by the parking controller to at least one of the smartdevice and a computerized third-party system a notification generated bythe parking controller in response to the second entry barrier beingopened, the notification indicating the entry of the first vehicle inassociation with the smart device.
 21. The method of claim 1 comprisingreceiving by the parking controller a parking reservation requestassociated with the smart device and the parking lot.
 22. The method ofclaim 21 wherein receiving by the parking controller a parkingreservation request associated with the smart device and the parking lotcomprises receiving the parking reservation request from a computerizedparking reservation system.
 23. The method of claim 1 further comprisingdetermining by the parking controller a lot occupancy for the parkinglot by maintaining a count of the difference between the number ofauthorized entries and authorized exits.
 24. The method of claim 23further comprising communicating by the parking controller the lotoccupancy to a third-party computerized system.
 25. The method of claim24 wherein communicating by the parking controller the lot occupancy toa third-party computerized system comprises communicating to acomputerized parking reservation system.
 26. The method of claim 25comprising receiving by the parking controller from the computerizedparking reservation system a parking reservation request associated withthe smart device and the parking lot.
 27. The method of claim 3 furthercomprising closing the entry barrier by the parking controller inresponse to a third presence determined by the parking controller, thethird presence indicating that the first vehicle is present at aninterior side of the entry barrier.
 28. The method of claim 4 furthercomprising closing the exit barrier by the parking controller inresponse to a third presence determined by the parking controller, thethird presence indicating that the second vehicle is present at anexterior side of the exit barrier.
 29. The method of claim 1 furthercomprising communicating by the server to the smart device parking lotinformation associated with the parking lot, the parking lot informationcomprising the location of the parking lot.
 30. The method of claim 1further comprising communicating by the server to the smart device anotification of expiry of at least one of a parking session and aparking reservation.
 31. The method of claim 1 further comprisingcommunicating by the server to a third-party computerized system anotification of expiry of at least one of a parking session and aparking reservation.
 32. A computerized system for managing a parkinglot, the system comprising: (a) an entry beacon operable to transmit anentry-beacon identification of the entry beacon; (b) an exit beaconoperable to transmit an exit-beacon identification of the exit beacon,the exit beacon being selected from the group consisting of the entrybeacon and another beacon separate from the entry beacon; (c) a firstvehicle sensor operable to sense the presence of a first vehicle at avehicle entry location of the parking lot; (d) a second vehicle sensoroperable to sense the presence of a second vehicle at a vehicle exitlocation of the parking lot, the second vehicle sensor being selectedfrom the group consisting of the first vehicle sensor and anothervehicle sensor separate from the first vehicle sensor, the exit locationbeing selected from the group consisting of the entry location andanother location separate from the entry location, the second vehiclebeing the first vehicle or another vehicle separate from the firstvehicle; and (e) a computer-implemented server operable to receive froma smart device each of the entry-beacon identification and theexit-beacon identification, operable to determine the location of thesmart device in response to said each of the entry-beacon identificationand the exit-beacon identification, operable to determine a statusassociated with the smart device, operable to authorize an entry of thefirst vehicle when the status indicates no entry rejection of the smartdevice, the determined location of the smart device is at the entrylocation, and the first vehicle sensor senses the presence of the firstvehicle at the entry location, operable to determine an updated value ofthe status in response to a payment transaction associated with thesmart device, and operable to authorize an exit of a second vehicle whenthe status indicates no exit rejection of the smart device, thedetermined location of the smart device is at the exit location, and thesecond vehicle sensor senses that the second vehicle is at the exitlocation.
 33. The system of claim 32 wherein the parking lot has anentry barrier for regulating entries at the entry location, wherein thesystem comprises an entry controller operable to open and close theentry barrier, and wherein the server is operable to cause the entrycontroller to open the entry barrier when the server authorizes theentry of the first vehicle.
 34. The system of claim 32 wherein theparking lot has an exit barrier for regulating exits at the exitlocation, wherein the system comprises an exit controller operable toopen and close the exit barrier, and wherein the server is operable tocause the exit controller to open the exit barrier when the serverauthorizes the exit of the second vehicle.
 35. The system of claim 33wherein the parking lot has an exit barrier for regulating exits at theexit location, the exit barrier being selected from the group consistingof the entry barrier and another barrier separate from the entrybarrier, wherein the system comprises an exit controller operable toopen and close the exit barrier, the exit controller being selected fromthe group consisting of the entry controller and another controllerseparate from the entry controller, and wherein the server is operableto cause the exit controller to open the exit barrier when the serverauthorizes the exit of the second vehicle.
 36. The system of claim 32wherein the server is operable to determine a parking fee associatedwith the smart device in response to a duration of time spent parking.37. A computerized system for managing a parking lot, the systemcomprising: (a) means for authorizing an entry of a first vehicle inresponse to a status indicating no entry rejection of a smart device, afirst location indicating the smart device is located at an entrylocation of the parking lot, and a first presence indicating that thefirst vehicle is present at the entry location; (b) means fordetermining an updated value of the status in response to a paymenttransaction associated with the smart device; and (c) means forauthorizing an exit of a second vehicle in response to the statusindicating no exit rejection of the smart device, a second locationindicating that the smart device is located at an exit location of theparking lot, and a second presence indicating that the second vehicle ispresent at the exit location, the exit location being selected from thegroup consisting of the entry location and another location separatefrom the entry location, the second vehicle being the first vehicle oranother vehicle separate from the first vehicle.
 38. The system of claim37 comprising means for determining whether the second vehicle is thefirst vehicle.
 39. A computer-implemented method of managing a parkinglot, the method comprising: (a) authorizing an entry of a first vehicleby a computerized parking controller in response to a status indicatingno entry rejection of a smart device, a first location indicating thatthe smart device is located at an entry location of the parking lot, anda first presence indicating that the first vehicle is present at theentry location, the first location being determined by a location sensorof the parking controller, the location sensor being operable todetermine the location of the smart device when the smart device iswithin a near-field range of the location sensor, the location sensorcommunicating the first location to a server of the parking controller;(b) determining by the parking controller an updated value of the statusin response to a payment transaction associated with the smart device;and (c) authorizing an exit of a second vehicle by the parkingcontroller in response to the status indicating no exit rejection of thesmart device, a second location indicating that the smart device islocated at an exit location of the parking lot, and a second presenceindicating that the second vehicle is present at the exit location, thesecond location being determined by the location sensor, the locationsensor communicating the second location to the server, the exitlocation being selected from the group consisting of the entry locationand another location separate from the entry location, the secondvehicle being the first vehicle or another vehicle separate from thefirst vehicle.
 40. The method of claim 39 wherein step (a) comprisesdetermining by the location sensor the first location by trilaterationof at least one first communication between the smart device and aplurality of wireless communication devices of the location sensordisposed at the parking lot, and wherein step (c) comprises determiningby the location sensor the second location by trilateration of at leastone second communication between the smart device and the plurality ofwireless communication devices.
 41. The method of claim 40 wherein step(a) of claim 39 comprises effecting said at least one firstcommunication by near-field wireless communications, and wherein step(c) comprises effecting said at least one second communication bynear-field wireless communications.
 42. The method of claim 39 whereinstep (a) comprises determining by the location sensor the first locationby proximity sensing the smart device by a first proximity sensor of thelocation sensor disposed at the parking lot, and wherein step (c)comprises determining by the location sensor the second location byproximity sensing the smart device by a second proximity sensor of thelocation sensor disposed at the parking lot, the second proximity sensorbeing selected from the group consisting of the first proximity sensorand another proximity sensor separate from the first proximity sensor.43. The method of claim 39 wherein step (a) comprises determining by thelocation sensor the first location by establishing near-fieldcommunication between the smart device and a first NFC device of thelocation sensor disposed at the parking lot, and wherein step (c)comprises determining by the location sensor the second location byestablishing near-field communication between the smart device and asecond NFC device of the location sensor disposed at the parking lot,the second NFC device being selected from the group consisting of thefirst NFC device and another NFC device separate from the first NFCdevice.